Getting FSUM7351 not found error running OPS/MVS Event Management and Automation UNPAX JCL listed in the Install guide.
search cancel

Getting FSUM7351 not found error running OPS/MVS Event Management and Automation UNPAX JCL listed in the Install guide.

book

Article ID: 5829

calendar_today

Updated On:

Products

OPS/MVS Event Management & Automation

Issue/Introduction

When running the sample UNPAX JCL listed in the Install guide section of the OPS/MVS Event Management and Automation Installation PDF, I am getting the following errors:

CD: FSUM7351 not found
PAX: FSUM7351 not found

//*********************************************************************
//* THIS SAMPLE JOB CAN BE USED TO INVOKE THE PAX COMMAND TO CREATE         *
//* THE PRODUCT-SPECIFIC INSTALLATION DIRECTORY.                                           *
//*                                                                                                                         *
//* THIS JOB MUST BE CUSTOMIZED AS FOLLOWS:                                                   *
//* 1. SUPPLY A VALID JOB STATEMENT.                                                                   *
//* 2. REPLACE "YOURUSSPAXDIRECTORY" WITH THE NAME OF THE USS                    *
//* DIRECTORY USED ON YOUR SYSTEM FOR PAX ESD DOWNLOADS.                         *
//* 3. REPLACE "PAXFILE.PAX.Z" WITH THE NAME OF THE PAX FILE.                           *
//* NOTE: IF YOU CONTINUE THE PARM= STATEMENT ON A SECOND LINE,                 *
//* START ENTERING CHARACTERS IN COLUMN 16 AND MAKE SURE                           *
//* THE 'X' CONTINUATION CHARACTER IS IN COLUMN 72.                                        *
//*********************************************************************
//UNPAXDIR EXEC PGM=BPXBATCH,
// PARM='SH CD /u/.../; PAX -RVF B60000ESACS.PAX'
//*UNPAXDIR EXEC PGM=BPXBATCH,
//* PARM='SH CD /YOURUSSPAXDIRECTORY/; PAX X
//* -RVF PAXFILE.PAX.Z'
//STDOUT DD SYSOUT=*
//STDERR DD SYSOUT=*

 

Environment

OPS/MVS Event Management and Automation 13.0 Incremental release

Cause

UNIX parameters in the JCL need to be lower case (case sensitive).

Resolution

JCL did not work on the mainframe was due to UNIX parameters in the JCL needing to be lower case (case sensitive).

Change this:
// PARM='SH CD /u/.../; PAX -RVF B60000ESACS.pax.Z'

To this:
// PARM='sh cd /u/.../; pax -rvf B60000ESACS.pax.z'
 

Additional Information

1) Remember to ftp your pax files to your unix directory with the .z extension.
2) Remember to make sure your JCL statement for the UNPAX job maintains the UNIX parameters in lowercase: sh, cd, pax, -rvf, pas.z.

Reference:

Review the following section of the applicable product documentation:   Create a Product Directory from the Pax File