Job DSNTEJ1P

DSNTEJ1P precompiles, compiles, and link-edits PL/I program DSNTEP2. This program then lists the sample database tables and views. It is a dynamic PL/I program that accepts SQL statements. It produces a listing of the results of SELECT statements.

Tip: If you already ran job DSNTEJ1L, you do not need to run DSNTEJ1P because these jobs produce the same results. The major difference is that DSNTEJ1P uses the PL/I compiler and allows you to customize DSNTEP2 and DSNTEP4.

If you do run job DSNTEJ1P after job DSNTEJ1L, and you previously bound the packages that were produced by job DSNTEJ1L at multiple sites, you also need to bind the packages that are produced by job DSNTEJ1P at the same sites. Otherwise, you will receive SQLCODE -805 errors when you use DSNTEP2 or DSNTEP4 to access data at the remote sites.

If DSNTEJ1P runs successfully, it produces the return codes that are shown in the table below.

Table 1. DSNTEJ1P return codes
Step PROCSTEP Return code
PH01PS01
PPLI
PC
PLI
PLKED1
LKED
0000
0000
0000
0004
0000
PH01PS02   0000 or 0004
PH01PS03
PPLI
PC
PLI
PLKED1
LKED
0000
0000
0000
0004
0000
PH01PS04   0000 or 0004
Note:
  1. The PLKED step does not exist in the job if the value of the PL/I LE PRELINKER PHASE field is set to NO.

You can compare the output from this job with the sample output for DSNTEJ1P, which is found in member DSN8TJ1P in your prefix.SDSNIVPD data set.

If you run DSNTEJ1L before DSNTEJ1P, you can expect step PH01PS02 of job DSNTEJ1P to produce a return code of 0004 and the following message:

SQLWARNING ON GRANT   COMMAND, EXECUTE FUNCTION
  RESULT OF SQL STATEMENT:
  DSNT404I SQLCODE = 562, WARNING:  A GRANT OF A PRIVILEGE WAS IGNORED
           BECAUSE THE GRANTEE ALREADY HAS THE PRIVILEGE FROM THE GRANTOR

If either DSNTEJ1 or DSNTEJ1P fails or abends, ensure that the user that is specified in the JOB statements is an authorized ID. If the name that you specified for either SYSTEM ADMIN 1 or SYSTEM ADMIN 2 on installation panel DSNTIPP1 is a primary authorization ID, use this name. If the sample authorization exit routine and RACF® are installed, and if the SYSTEM ADMIN 1 and SYSTEM ADMIN 2 are known to Db2 as secondary authorization IDs, you can run these jobs under a user ID in either of these RACF groups.

Then, correct any other problems. Before rerunning DSNTEJ1, run DSNTEJ0 to drop the sample data. If you rerun DSNTEJ1P, rerun it from the last successful step.