Re: Issues with SAVRST* -- MIDRANGE-L

Thanks (Evan and Bryan as well),

Checking the logs on System A I see the following:

Program start request received on communications device SYSTEMB wasrejectedProgram start request on mode QSOCCT of device description SYSTEMBrejected.


Detail on the first error is:

Message ID . . . . . . :CPF1269Date sent . . . . . . : 07/27/06 Time sent . . . . . . :08:30:04Message . . . . : Program start request received on communicationsdeviceSYSTEMB was rejected with reason codes 711,1502.Cause . . . . . : The program start request was rejected injob548321/QUSER/SYSTEMB. The device belongs to remote location SYSTEMB.If thedevice is an advanced program-to-program communications (APPC)device, theprogram start request was received on mode QSOCCT withunit-of-workidentifier SYSNET.SYSTEMB-BF29C1A99BA5-0001. The first reason codemeans:User is not authorized to library on library list. The second reasoncodemeans: Procedure notfound.Recovery . . . : See the job log for more information about theproblem.So I tracked down the job log and it turned out that SYSTEMA has alibrary in the library list that QUSER isn't authorized to. I am notsure what was putting that library into the library list, I'll trackthat down next, but authorizing QUSER to use the library (temporarily)took care of the problem.

Thanks for the pointers. I should have reviewed the system messagesmore carefully.


Pete



Urbanek, Marty wrote:

Pete,

Sense code 080F says check out your security stuff, i.e. user ids & passwords 
being used both directions, are they the same, is anything *disabled, do they have 
authority to the target program? Also DSPLOG like Bryan said, for evoke failure 
messages.

-Marty

------------------------------

date: Wed, 26 Jul 2006 16:13:53 -0600
from: Pete Helgren <Pete@xxxxxxxxxx>
subject: Issues with SAVRST*
I have a customer with a partitioned i5. I set up the two partitions sothat I could use the SAVRST commands to move data between thepartitions. But, I have only been able to pass data one way and I amnot sure why. On system A I can use STRPASTHR to System B and theSAVRST* commands. On System B I can use STRPASTHR to System A but Icannot use any SAVRST commands. Instead I get an error: "CPFAD8B - Anerror occurred during the SAVRSTLIB operation." The job log shows anerror "Communications failure. Session was not started." (CPF8911) -Cause . . . . . : The system has detected a communications failure.The sense code is X'080F6051'.Poking around a bit hasn't revealed much to me. I compared the setup ofboth partitions, and except for system names, they *look* identical. Ican ping System A from System B. I can telnet from system B to systemA. I cannot APING from System B to System A. I first get "Allocatetook .010 seconds." and then "Command did not complete successfully."Job log shows error: CPD3B4D "Target program currently not available"
Not sure what I am missing here. I have set this up before in differentlocations and it has pretty much worked, right out of the box.
What should I be looking for?

Thanks,

Pete Helgren