Preparing JCL for running the Discovery Agent as an MVS job

To prepare the JCL for running the Discovery Agent as an MVS job, copy and customize the ZAGENT JCL sample that is provided. You can use this job for scanning and parsing STATIC file, DYNAMIC file, ROUTECARD file, and IdML Book file.

1. Use the following JCL sample to Copy ZAGENT and ZAGENT2 from USS to MVS. Change the #path in JCL to 4 JCL corresponding to different types of files.

   //OCOPY    JOB ,REGION=0M,MSGCLASS=C,MSGLEVEL=(1,1),NOTIFY=&SYSUID     
   //******************************************************************** 
   //* Copy HFS output files to SYSOUT, since BPXfile* can only write     
   //* STDOUT and STDERR to HFS files.                                    
   //******************************************************************** 
   //COPYSTEP EXEC PGM=IKJEFT01                                           
   //INHFS    DD PATH='#path/ZJOB/ZAGENT',   
   //         PATHOPTS=(ORDONLY)                                          
   //OUTMVS   DD DSN=#jcldataset(ZAGENT),DISP=SHR                    
   //SYSTSPRT DD SYSOUT=*                                                 
   //SYSTSIN  DD *                                                        
   OCOPY INDD(INHFS) OUTDD(OUTMVS) TEXT CONVERT(YES) PATHOPTS(USE)        
   /*            

   #path

   Specifies the absolute path under USS where the Discovery Agent package is decompressed or copied. For example discovery-agent-static, discovery-agent-dynamic, or discovery-agent-idml folder.

   #jcldataset

   Specifies the JCL library on MVS where you want to put the JCLSCAN file. You can use an existing JCL library, or create a new JCL library before you copy this JCL file.

   Note: You can perform the same steps to copy ZAGENT2 to the same JCL DATASET.
2. In the ZAGENT dataset member, make the following changes:
   1. Replace all occurrences of #path with the IBM z/OS UNIX System Services directory in which the discovery_agent.jar and discovery_agent.sh files are stored.
   2. Replace all occurrences of /usspath with the IBM z/OS UNIX System Services path in which standard output and standard error that are produced by the discovery_agent.sh script are to be stored.
   3. In all occurrences of user.ZAGENT.*, replace user with the high-level qualifier of the MVS dataset in which you want to store standard output and standard error that are produced by the ZAGENT JCL.
   4. Replace file* with the value FILE.
   5. Set the correct path location for JAVA_HOME by replacing #java_home.
   Important: The ZAGENT JCL does not support long path names as values for #path and /usspath. The following problems can occur if these path names are too long:

   • The JCL might not accept the values for #path and /usspath if they cause the line length to exceed the limit that is defined in the dataset. This limit is usually 80 characters.
   • The JCL might not run.

   To prevent these problems, ensure that the Discovery Agent is installed into a directory with the shortest possible path name. If that is not possible, run the following commands to create a symbolic link with a short path name, and use that symbolic link as the value for #path and /usspath:

   cd/
   In -s long_path_to_agent_directory short_symlink_path