Rational Developer for System z
Enterprise COBOL for z/OS, Version 4.1, Programming Guide


Example: JCL for compiling using HFS

The following job uses procedure IGYWC to compile a COBOL program demo.cbl that is located in the hierarchical file system (HFS). It writes the generated compiler listing demo.lst, object file demo.o, and SYSADATA file demo.adt to the HFS.

//HFSDEMO JOB ,
// TIME=(1),MSGLEVEL=(1,1),MSGCLASS=H,CLASS=A,REGION=50M,
// NOTIFY=&SYSUID,USER=&SYSUID
//COMPILE EXEC IGYWC,
// PARM.COBOL='LIST,MAP,RENT,FLAG(I,I),XREF,ADATA'
//SYSPRINT DD PATH='/u/userid/cobol/demo.lst',    (1)
// PATHOPTS=(OWRONLY,OCREAT,OTRUNC),              (2)
// PATHMODE=SIRWXU,                               (3)
// FILEDATA=TEXT                                  (4)
//SYSLIN DD PATH='/u/userid/cobol/demo.o',
// PATHOPTS=(OWRONLY,OCREAT,OTRUNC),
// PATHMODE=SIRWXU
//SYSADATA DD PATH='/u/userid/cobol/demo.adt',
// PATHOPTS=(OWRONLY,OCREAT,OTRUNC),
// PATHMODE=SIRWXU
//SYSIN DD PATH='/u/userid/cobol/demo.cbl',
// PATHOPTS=ORDONLY,
// FILEDATA=TEXT,
// RECFM=F
(1)
PATH specifies the path name for an HFS file.
(2)
PATHOPTS indicates the access for the file (such as read or read-write) and sets the status for the file (such as append, create, or truncate).
(3)
PATHMODE indicates the permissions, or file access attributes, to be set when a file is created.
(4)
FILEDATA specifies whether the data is to be treated as text or binary.

You can use a mixture of HFS (PATH='hfs-directory-path') and MVS data sets (DSN=traditional-data-set-name) on the compilation DD statements shown in this example as overrides. However, the compiler utility files (DD statements SYSUTx) and COPY libraries (DD statements SYSLIB) must be MVS data sets.


Terms of use | Feedback

This information center is powered by Eclipse technology. (http://www.eclipse.org)