3.3 Allocating Data Sets on the z/OS File System

Sequential or partitioned data sets can be used in COBOL and SQR processing. The DISP parameter in the JCL is critical to the successful execution of a JCL job submission and very sensitive to the data set disposition at the initiation of the job. For this reason, Oracle strongly recommends the use of a partitioned data set, rather than sequential data sets—particularly for output files —and for input files, when the existence of the actual file drives the processing path that the program takes.

An invalid file disposition in the process can prevent that process and all the processes from executing successfully. For this reason, Oracle recommends using DISP=SHR in your JCL DD statements. DISP=SHR presumes that the data set exists at the time a job execution is initiated. If the data set does not exist, a JCL error occurs. The PDS requires only the root data set--the individual member does not need to exist. If the member does not exist, it is automatically created by the z/OS file management system.

You should allocate partitioned data sets that include the following attributes:

• The record format should be variable block (RECFM=VB).

• The record length should be slightly wider than the record length of the file, which is defined within the SQR itself.

  Refer to the table below for SQR LRECL definitions.

• The data set name type should be PDS (DSORG=PO).

The following is an example of a JCL statement to allocate a PDS:

//*
//PDSALL   DD DSN=PSHLQ.PPVVV.SQRFILES,
//           DISP=(,CATLG,DELETE),
//           DCB=(DSORG=PO,RECFM=VB,LRECL=500),
//           VOL=SER=,
//           SPACE=(TRK,(200,95,75),RLSE),
//           UNIT=SYSDA
// *

The following table details the information that you can use to both pre-allocate the data set and modify the JCL Shells for PeopleSoft FMS.

PeopleSoft Product	SQR or COBOL Program Name	DD Card Name1	Data Set Type / Record Format / Record Length	Member Name or Random Name
General Ledger	GLS7500	Defined and entered by the customer	PDS/VB/850	Specific Member name (OUTPUT FILE)
Treasury	ECIN0001	Defined and entered by the customer.	PDS/VB/500	Specific Member name (OUTPUT FILE)

¹ DD Card Name — File name passed from within the program; limited to 8 characters with no special characters.

The following tables detail the information that you can use to both pre-allocate the data set and modify the JCL Shells for PeopleSoft SCM products in the next section, Modifying the JCL Shells.

PeopleSoft Inventory:

SQR or COBOL Program Name	DD Card Name1	Data Set Type / Record Format / Record Length	Member Name or Random Name
INS9050	INCOUNT	PDS/VB/250	Specific Member name (INPUT FILE)
INS9051	INCOUNT	PDS/VB/250	Specific or Random Member name (OUTPUT FILE)
INS9080	INFCST	PDS/VB/250	Specific or Random Member name (OUTPUT FILE)
INS9081	INFCST	PDS/VB/250	Specific Member name (INPUT FILE)

¹ DD Card Name — File name passed from within the program; limited to 8 characters with no special characters.

PeopleSoft Manufacturing:

SQR or COBOL Program Name	DD Card Name 1	Data Set Type / Record Format / Record Length	Member Name or Random Name
SFS1100	SELPID	PDS/FB/183	Specific Member name (OUTPUT FILE)
SFS1600	SELPID	PDS/FB/183	Specific Member name (OUTPUT FILE)

¹ DD Card Name — File name passed from within the program; limited to 8 characters with no special characters.