ARSYSPIN running on different LPAR failing to use unified logon

[Nolan]

Opened a PMR but tossing it out here to see if anyone has thoughts.

We are trying to run ARSYSPIN on a different LPAR than ARSSOCKD. When the load starts it fails on

"ARS1607E The OnDemand stash file >< either does not exist or is not valid. Return Code=4."

We validated the SET PROG EXIT was pointing to the same library. I don't see any other settings that would stop it from working successfully. Can ARSYSPIN run on a different LPAR? If yes what settings to do I need to validate are set up beside the SET PROG? Note: the LPAR we are trying to run on is normally used for our test instance of CMOD. We did bring down the test server so there was no conflict.

Cheers

[Ed_Arnold]

Jayem - don't know if you've seen this one or not.  I wrote this some years ago and believe it might be applicable.

ARS.PTGN not active for ARSLOAD

http://www-01.ibm.com/support/docview.wss?uid=swg21192853

Ed

[Nolan]

I found an empty arsload.cfg file...but I have one on the LPAR that is working.  For kicks, I renamed the file and tried again.  No luck

ARS1607E The OnDemand stash file >< either does not exist or is not valid.  Return Code=4.

[Ed_Arnold]

Jayem -

a) have you verified this:

...it is important that the arsload owner has a unique OMVS uid defined...

b) have you verified all the steps 1-9?

Ed