Package Ship Facility › How to Enable USS Supported Files for Package Ship › Enable USS Supported Files for Package Ship

Enable USS Supported Files for Package Ship

Backout files and records are required to enable package outputs to be shipped using the Package Ship facility. For USS supported files, the ENUSSUTL utility creates the backout files and records. The processor that is associated to the element type must include the ENUSSUTL utility to collect and associate the backout files to the element.

Follow these steps:

1. Add the ENUSSUTL utility to the processor with the appropriate Copy and Select or Delete and Select statements.

   The ENUSSUTL syntax depends on whether it is used in a Move, Generate, or Delete processor. Move and Generate processors use Copy statements. Delete processors use Delete statements.

   • Move and Generate processors

     COPY syntax—Copy, Select group statements are used in Generate and Move processors. In a generate processor, copy the USS file from the CA Endevor SCM path location to a temporary path. Then use this file as input into the ENUSSUTL utility.

     Copy Indd dd-name  Outdd dd-name .
     Select File file-name [Newfile file-name].
     

     Copy Indd dd-name Outdd dd-name

     Identifies the dd-name copy source and target path locations.

     Indd dd-name

     Specifies the dd-name source location. CA Endevor SCM and user symbolics can be used on the JCL path name specification.

     Outdd dd-name

     Specifies the dd-name target location. CA Endevor SCM and user symbolics can be used on the JCL path name specification.

     Select FIle file-name

     Specifies the name of the file at the source location for the associated Copy statement. If the Newfile clause is not used, this file specification will be used at the target location. A file name can be up to 255 characters. See the SCL Reference Guide for information on how to specify a value that spans multiple 80 character lines. Multiple select statements can follow the copy statement. Copy and Select group statements are supported. Select statements are paired with the copy statement that precedes it. CA Endevor SCM and user symbolics can be used on the file name specification.

     Newfile file-name

     (Optional.) Specifies the copy file name to be used for the file at the target location. If this clause is not used, the file specification name is used. The name can be up to 255 characters. See the SCL Reference Guide for information on how to specify a value that spans multiple 80 character lines. CA Endevor SCM and user symbolics can be used on the file name specification.

     Sample syntax for Move processors:

     //COPY1   EXEC  PGM=ENUSSUTL
     //INPUT   DD  PATH=’input-pathame’
     //OUTPUT  DD  PATH=’output-pathname’,
     //        PATHMODE=(SIRWXU,SIRWXG,SIRWXO)
     //ENUSSIN   DD  *
       COPY INDD ‘INPUT’  OUTDD ‘OUTPUT’ .
       SELECT FILE ‘fileone.ext’ .
       SELECT FILE ‘filetwo.ext’ .
     

     Sample syntax for Generate processors:

     //BPXW1   EXEC  PGM=BPXBATCH
     //STDPARM DD  *
     //SH cp -B ‘pathname.&C1ELELMNT255.’ ‘temp-pathname.&C1ELELMNT255.’;
     //STDOUT  DD  SYSOUT=*
     //STDERR  DD  SYSOUT=*
     //COPY1   EXEC  PGM=ENUSSUTL
     //INPUT   DD  PATH=’temp-pathame’
     //OUTPUT  DD  PATH=’pathname’,
     //        PATHMODE=(SIRWXU,SIRWXG,SIRWXO)
     //ENUSSIN   DD  *
       COPY INDD ‘INPUT’  OUTDD ‘OUTPUT’ .
       SELECT FILE &C1ELELMNT255. .
     

     Rules for Copy syntax as are follows:

     • Multiple SELECT statements can follow the COPY statement.
     • Multiple COPY SELECT groups can be specified. Select statements are associated with the preceding Copy statement.

           COPY INDD ‘INPT1’  OUTDD ‘OUTP1’  .
           SELECT FILE ‘fileone.ext’  .
           SELECT FILE ‘filetwo.ext’  .
           COPY  INDD ‘INP2’  OUTDD ‘OUTP2’  .
           SELECT FILE ‘filethree.ext’ .
       

     • The JCL PATHOPTS parameter is ignored if used on the Copy DD JCL statements.
     • The PATHMODE parameter should be used on the OUTDD DD statement. If unspecified, the default filemode is set to ‘000’.
     • Concatenation of paths are not allowed on the INDD DD statement. The utility will check for this and if found will fail during syntax validation.
     • You cannot copy to the same path and file name.
     • By default, ENUSSUTL copies the USS file using the credentials of the Alternate ID, so the owner and group of the file after the copy is the Alternate ID. If you want to use the user's credentials instead code, ALTID=N on the processor step.
   • Delete processors

     DELETE Syntax—Use the utility’s Delete and Select group statements in a delete processor.

     Delete FRomDD dd-name .
     Select File file-name .
     

     Delete FRomdd dd-name

     Identifies the DELETE target path locations.

     FRomdd dd-name

     Specifies the FROM dd-name. CA Endevor SCM and user symbolics can be used on the JCL path name specification.

     Select FIle file-name .

     Specifies the name of the file to be deleted that is associated with the Delete statement. A file name can be up to 255 characters. See the SCL Reference Guide for information on how to specify a value that spans multiple 80 character lines. Multiple select statements can follow the delete statement. Delete and Select group statements are supported. Select statements are paired with the delete statement that precedes it. CA Endevor SCM and user symbolics can be used on the file name specification.

     Sample syntax for Delete processors:

     //DEL1    EXEC  PGM=ENUSSUTL
     //FROM    DD  PATH=’pathname’,
     //        PATHMODE=(SIRWXU,SIRWXG,SIRWXO)
     //ENUSSIN   DD  *
       DELETE  FROMDD ‘FROM’  
       SELECT FILE ‘fileone.ext’ .
       SELECT FILE ‘filetwo.ext’ .
     

     Rules for Delete syntax as are follows:

     • Multiple SELECT statements can follow the DELETE statement.
     • Multiple DELETE SELECT groups can be specified. Select statements are associated with the preceding Delete statement.

           DELETE FROMDD ‘FROM1’       .
           SELECT FILE ‘fileone.ext’   .
           SELECT FILE ‘filetwo.ext’   .
           DELETE FROMDD ‘FROM2’       .
           SELECT FILE ‘filethree.ext’ .
       

     • The JCL PATHOPTS parameter is ignored if used on the Delete DD JCL statements.
     • Concatenation of paths are not allowed on the FROMDD DD statement. The utility checks for this and if found will fail during syntax validation.
     • By default, ENUSSUTL deletes the USS file using the credentials of the Alternate ID, so the Alternate ID must have appropriate access to the from path. If you want to use the user's credentials instead code, ALTID=N on the processor step.
2. (Optional) Include the NOECHO parameter on the EXEC statement, if you want to suppress the echo of ENUSSUTL commands produced by the parser from appearing in the C1MSGS1 output.

   NOECHO

   Suppresses the SCL statements from appearing in the C1MSGS1 output.

   For example, the following EXEC statement includes the NOECHO parameter and will prevent the ENUSSUTL commands from appearing in the C1MSGS1 output:

   //STEPxx  EXEC PGM=ENUSSUTL,PARM=’NOECHO’