As you can anticipate, we typically take the NetviewFtp members of Endevor's CSIQOPTN library and convert them into IBM FTP members. We choose the NetviewFTP members only because they have the "FTP" in the member names.
For example, the #PSNFTPJ member would be changed to execute FTP and might look like this.....
//*----PACKAGE SHIPMENT JOB #2 -------------------------- #PSNFTPJ
@REM ****************************************************** #PSNFTPJ ***
@REM * CONTENTS: ENDEVOR/MVS - JCL TO TRANSMIT DATASET
@REM *******************************************************************
//* MY DESTNODE = &NODENAME #PSNFTPJ
//*---------------------------------------------------------- #PSNFTPJ
//* EXECUTE FTP COMMANDS ------------------------------------ #PSNFTPJ
//*---------------------------------------------------------- #PSNFTPJ
//FTP EXEC PGM=FTP,REGION=2048K,TIME=800 #PSNFTPJ
//NETRC DD DISP=SHR,DSN=&SYSUID..ENDEVOR.NETRC(SHIPPING)
//SYSTSPRT DD SYSOUT=*
//SYSPRINT DD SYSOUT=*
//SYSUDUMP DD SYSOUT=Q
//OUTPUT DD SYSOUT=* #PSNFTPJ
//SYSIN DD * #PSNFTPJ
It is a good idea to comment the members thoroughly. If you can, use SFTP. If not and staying with FTP, then at least use a NETRC file for logon credentials..
You may have to change some CSIQSENU members as well. In the C1BMXJOB member you can concatenate libraries. For example if you place your modified CSIQOPTN members in a library by themselves, then you can concatenate your library above the others in C1BMXJOB for the C1BMXFTM ddname.
A popular exit we provide can automate the submission of package shipment jobs when packages are Approved, Backed out or Backed in.
If you would like more on any of this, just indicate so and I will add to the posting here
Original Message:
Sent: 02-02-2021 10:04 AM
From: Joseph Walther
Subject: Package Ship Alternatives
Hello Nancy. A couple of quick responses:
- FTP has been successfully configured with Endevor package shipping, and supports shipments of PDSEs and shipments of package backouts.
- Deploy to Test can be used in conjunction with package shipping, but it is not required. A local transmission would not be necessary if processors (typically MOVE processors) can cause the necessary automated actions.
Original Message:
Sent: 02-01-2021 04:57 PM
From: Nancy Rumsey
Subject: Package Ship Alternatives
Hi
We are setting up Endevor 18.0.12 and are in the process of trying to setup Package Ship for our customer. And have found we cannot ship the load libraries through netvftp or BDT. They do not support program object PDSEs. The only options left are Connect:direct and XCOM, which neither are installed or used by anyone on this system. Also there is no shared dasd between the development and production Lpars.
So my question is, what is the best process to use to ship packages, that will allow for backouts . We would prefer to use XMIT or FTP instead.
In addition , this customer is looking at the Deploy for test, which I understand uses the package ship premise. But since our test systems are all on the same LPAR, we would be using a LOCAL transmission, this should not be a problem. Correct?
We are open to any alternative package options, since the timeline and cost to install connect:direct or XCOM is not ideal.
Thank you
Nancy