Here is how…
In this example, I would like to get all CA Datacom/AD Version 15.0 solutions. I ordered solutions for AD 15.0 base components in (CA Datacom/AD, CA Datacom/DB, CA DATACOM DATADICTIONARY, CA DATACOM SQL, and CA IPC) from "CA Datacom/CA Ideal/CA IPC Maintenance Grid for z/OS" Product Name/Release "CA Datacom/AD Version 15.0" PTFs Available Since 0000
When the solution order was ready and was give the order number, I selected the “PREFERRED FTP” method which does not create a scart0.zip:
FTP location: /siteid/ordernumber
Note that when ordering solutions, there may be 3 kinds of files given:
- The module solutions as ROnnnnn.BIN
- The informational solutions as RInnnnn.txt
- The ERROR HOLD information as ROnnnnn.HOLDDATA.TXT
I used the following batch FTP for that solution order…
The locsite sets up the storclass, space, and DCB for the MVS data sets.
The lcd ‘dsnhlq’ specifies the HLQ for the MVS data sets to be created.
The mget creates… or replaces when using “(rep”… a sequential FB 80 data set per PTF.
//FTP EXEC PGM=FTP,REGION=0M,PARM=' (time 40'
//SYSPRINT DD SYSOUT=*
//OUTPUT DD SYSOUT=*
//SYSIN DD *
locsite CYL primary=001 secondary=001 ucount=1
locsite recfm=FB lrecl=80 blksize=0
mget *.txt (rep
mget *.BIN (rep
The FTP of this example order created the MVS data sets on storclass TSO volumes as fixed block80
dsnhlq.ROnnnnn.BIN <- each PTF in an MVS data set