On 20-Oct-2014 14:19 -0500, Darryl Freinkel wrote:
Scenario:
We use a production and development system. I wrote a tool to promote
code from the development LPAR to the production LPAR. The process
uses DDM heavily. This process has worked without incident for the
past 3 years.

We moved data centers and as a result, we changed our IP addresses on
the system.

Problem:
The code (in a CL program) creates a DDM dataarea on the source
system to the target system (production). That data area stores a
sequential number. The program uses RTVDTAARA QTEMP/remote_dataarea
to retrieve the value.

We are now getting a CPF101A error for the RTVDTAARA and the process
thus fails. The second level text indicates that the error code is 17
which is the DDM user ID and passwords are required. We do use user
ID and password.

By any chance does that mean to imply that a _previously listed_ message, logged prior to the msg CPF101A had second level text with an EC17? Perhaps the symptom msg CPF9190 RC17 describes the 2nd level text from the previous message, rather than replacement text from the CPF101A itself?

We made no changes here. The DDM setup uses a RDB connection over
TCPIP. All other DDM commands work like they should. I use SBMRMTCMD
successfully with the exception now of the RTVDTAARA which can only
be used in the local environment on the source system.

The output from the prompted Change DDM TCP/IP [Server] Attributes (CHGDDMTCPA) are as expected?

Does any know what is causing the this error?

After whatever was the effective migration, might there exist a requirement to update the Server Authorization Entry; i.e. issue new Add Server Auth Entry (ADDSVRAUTE) requests for the user(s)?


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.