Endevor

This probably sounds elementary, but if I have a package shipment destination defined and want to change the 'remote nodename' to something else once I have completed testing. Are there any hidden repercussions I have not found in the documentation to doing this. We are splitting an LPAR and catalog and I want to have the package ship process complete before the split. So my plan was to get it completely working and shipping to a test LPAR with separate catalog. When the 'real' LPAR split happens, I can just change the node and carry on. Everything will be mapped to the same dataset names, etc. Only the remote node would change. Any thoughts or 'heads up' would be appreciated.

Chuck -  looks like you have taken everything into consideration.  what are you changing Connet:direct to?  remember there are only a few protocols that can be used:  CA XCOM, Bulk Dat Transfer using NJE/NJI, Bulk Data Transfer Version 2, Local, and Netview FTP.  you will need to modify all your destinations so that they point to the new protocol. If during your testing and you have any questions call before you go to production.  just make sure that all the datasets and authority for the ship and confirmation work on the new split lpars.

Give me a call if you need anything further 

Paul Lewis

Endevor Support

508-628-8148

I will not be changing protocols, they will both be connect:direct, only the node name changes.

Chuck -  after your comment about node i am confused since i only see node being part 

of the naming conventions.  can you give me call to clarify.

thanks  

Paul Lewis

Paul, whats your number ?

508-628-8148

I have successfully done this in the past and it has not caused any issues when you update your destination for the NODE NAME or even protocol.

Phon

Thank you all, I am glad this has been done in the past and feel better about my path forward.

Hi,

Right, There is no problem report when changing the Node name.

Regards,

Ollivier

Just a FYI - we're converting to COBOL 6 and I'm using PDSE type2 for the load libraries...

Connect Direct does not support this

"at this time CD z/OS (all versions) do not support PDSE V2 because dynamic allocation does not support it"

We have an RFE (Request for enhancement) for this "feature".

So I will have to PDSEv1 to PDSEv2 IEBCOPY.

Thanks for this update Steve