Server Guide


Step 3: Running the load module in OS/390

You can run the load module either in the batch environment, by editing the ABTBEXEC JCL, or by running it from a TSO command line. To run the job in batch, copy member ABT.V4R5M0.SABTJLIB(ABTBEXEC) into a user data set. Edit the copied member and specify the following:

If you are using data sets for input or output, you must provide DCB information for them. For example:

//OUTFILE    SYSOUT=*,DCB=(LRECL=80,RECFM=FB,BLKSIZE=3120)

The //DSNTRACE DD statement is considered optional. When this DD statement is present, DB2 generates a trace of DB2 CAF activity between the application and DB2. Under normal processing, comment out this statement to reduce overhead. If you are encountering errors that might be associated with DB2, specify the statement in your JCL.

Submit the job. Entries written to the Transcript will appear in the SYSPRINT data set of the job.

To run the job from the TSO command line, use the CALL command to access the load module. The CALL command should be part of a CLIST that you write to access the correct files and stack dump data set. For example, the following CLIST, named READSEQ, will allocate the stack dump data set and the sequential file being read. It will then call the load module that will read all the records from the sequential file.

ALLOCATE FILE(STAKDUMP) DA('ABT.TPO3.CICS1.STAKDUMP') SHR      
ALLOCATE FILE(SEQSPLT) DA('USERID.TEST.VARLEN(SEQSPLT)') SHR REU
CALL 'ABT.CICSTEST.SABTCLOD(SEQREAD)'                          
FREE F(STAKDUMP)                                               
FREE F(SEQSPLT)                                                

The output of the CLIST will appear on the TSO screen.


[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]