z/OS Language Environment Customization
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Making the cataloged procedure library available to your jobs

z/OS Language Environment Customization
SA38-0685-00

Language Environment is shipped with a procedure library, CEE.SCEEPROC, that contains several procedures that can be used during application development with Language Environment. These procedures are summarized in Table 1:

Table 1. Language Environment invocation procedures in CEE.SCEEPROC
Procedure Purpose
AFHWL Link-edit a Fortran program.
AFHWLG Link-edit and run a Fortran program.
AFHWN Change any external names in conflict between C and Fortran to the Fortran-recognized name.
AFHWRL Separate the nonshareable and shareable parts of a Fortran object module, and link-edit.
AFHWRLG Separate the nonshareable and shareable parts of a Fortran object module, link-edit, and execute.
CEEWG Load and run a non-XPLINK Language Environment-conforming application.
CEEWL Link-edit a non-XPLINK Language Environment-conforming application.
CEEWLG Link-edit and run a non-XPLINK Language Environment-conforming application.
CEEXL Link-edit an XPLINK Language Environment-conforming application.
CEEXLR Link-edit and run an XPLINK Language Environment-conforming application.
CEEXR Load and run an XPLINK Language Environment-conforming application.
EDCGNXLT (alias of EDC4P006) Read a genxlt file and produce the translation table which is stored in the nominated LOADLIB.
EDCICONV (alias of EDC4P007) Convert the characters from the input file from a coded character set definition to another character set definition and write the characters to the output file.
EDCLIB (alias of CRTCP002) Maintain a C/C++ object code library.
EDCPL (alias of EDC4P002) Prelink and link-edit a C/C++ application.

There are three ways to make the procedures available to your jobs. The method you choose depends on the special requirements and policies at your site. Use Table 2 to choose which method to use at your site.

Table 2. Deciding how to make cataloged procedures available to your jobs
If Then Result
You plan to use the IBM-supplied defaults and install into the default private procedure library. Modify the JES2 start procedure. Makes all procedures in the libraries available to any job in the system.
You are not using all the defaults and you want to choose which of the procedures to make available to general users. Copy the procedures into a system or private PROCLIB. Makes the procedures available to your installation jobs.
You are not using all the defaults. Use the procedures as inline procedures. Inserts the appropriate procedure into each job.

The process is as follows:

  1. Modify the JES start procedure. You can do either of the following tasks:
    • Add a new //PROCnn DD statement for the Language Environment procedure library, CEE.SCEEPROC.
    • Concatenate the procedure library to the //PROC00 DD statement.

    While testing, you can use the /*JOBPARM statement with the PROCLIB= parameter to make sure that your jobs use procedures from the correct library. To learn how to do this, see the section on JES2 control statements in z/OS MVS JCL Reference.

    All procedures in the libraries that are added to the JES2 start procedure are available to any job in the system. The JES2 procedure is usually member JES2 in SYS1.PROCLIB.

  2. Place cataloged procedures in a system or private PROCLIB. Copy the system procedures from the default libraries into an already-cataloged procedure library. You can use SYS1.PROCLIB as your cataloged procedure library. The copied procedures are callable by your installation jobs. However, procedures copied into a PROCLIB outside of SMP/E control are more difficult to maintain.

    You can use the JCLLIB statement to specify a private PROCLIB. Do this by including the following statement after the JOB card and before the first EXEC statement in the job: //PROCLIB JCLLIB ORDER=(CEE.SCEEPROC)

  3. Use cataloged procedures as inline procedures. Modify the procedure to reflect the high-level qualifiers you are using for the installation, and save your changes. Edit each job before you submit it, and copy the procedure into the job (inline).

    Be sure to place // PEND at the end of the inline procedure.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014