Db2 Installation Jobs (DSNTIJxx)

How tailored jobs fit the install flow

After the CLIST finishes, open the NEW sample library and read the job prologs. IBM’s Installation and Migration Guide lists a recommended order. A simplified mental model is: tell z/OS about Db2, define and initialize system data sets, build parameter modules, start Db2, tailor the catalog, create work files and objects, set up routines, then back up and verify.

1
2
3
4
5
6
7
8
9
10
11
12
/* Conceptual early sequence (exact members vary by release) */
DSNTIJMV   /* define to IRLM and MVS */
DSNTIJIN   /* define system data sets */
DSNTIJUZ   /* ZPARM module */
DSNTIJUA   /* application defaults module (often with UZ) */
DSNTIJUM   /* message CCSID module */
DSNTIJID   /* initialize system data sets */
/* ... connect attachments, start Db2 ... */
DSNTIJTC   /* catalog tailor */
DSNTIJSG   /* objects and binds */
DSNTIJRT   /* supplied routines */
DSNTIJIC   /* catalog/directory image copy */

Core jobs you will see often

DSNTIJIN — define system data sets

DSNTIJIN defines the VSAM and related system data sets the subsystem needs. Failures here are usually SMS, catalog alias, or space problems foreshadowed on DSNTIPA2–A4. Fix the definition cause; do not skip ahead to catalog jobs.

DSNTIJUZ — subsystem parameters

DSNTIJUZ defines the data-only subsystem parameter module (often thought of as the ZPARM load module). It expands macros such as DSN6ARVP, DSN6FAC, DSN6GRP, DSN6LOGP, DSN6SPRM, and DSN6SYSP using values collected on the panels. In data sharing, each member needs its own module and therefore its own tailored DSNTIJUZ.

DSNTIJMV — define Db2 to z/OS

DSNTIJMV introduces Db2 to IRLM and MVS: subsystem definitions, procedures, and related PARMLIB/PROCLIB updates. Coordinate with system programmers. Some environments can refresh definitions dynamically; others need an IPL before the first start.

DSNTIJID — initialize system data sets

After definition, initialization jobs such as DSNTIJID (with related members like DSNTIJIE and DSNTIJIF on many paths) format or initialize BSDS and log structures so Db2 can start cleanly. These jobs sit after parameter modules exist and before you expect a successful cold start.

DSNTIJTC — catalog tailor

DSNTIJTC runs catalog maintenance (CATMAINT) to bring the catalog to the level required for the install or migration step. On modern continuous-delivery releases, catalog level and function level interact carefully—read the guide for your target function level before treating RC=4 messages as failures.

DSNTIJSG — objects and binds

DSNTIJSG defines and binds Db2-supplied objects used for tools such as SPUFI and DCLGEN and related user-maintained database activity. It is the bridge from “engine starts” to “administrators can use familiar Db2I tools.”

DSNTIJRW, DSNTIJRT, DSNTIJRV — routines path

DSNTIJRW helps define core WLM application environments for Db2-supplied stored procedures. DSNTIJRT installs and configures those routines using DSNTRIN. DSNTIJRV verifies them. Routine creator and security fields from installation preference panels matter especially for these jobs.

DSNTIJIC — protect the catalog

DSNTIJIC takes image copies of the directory and catalog. Disk versus tape choices on preference panels change whether the job uses parallel LISTDEF/TEMPLATE patterns or more serial tape-oriented JCL. Run it after the catalog is tailored and healthy.

DSNTIJUM — message CCSID module

DSNTIJUM defines the offline message generator CCSID module (DSNHMCID). It often runs with the other initialization-parameter jobs such as DSNTIJUZ and DSNTIJUA.

Special and release-specific jobs

DSNTIJCB historically supports BSDS conversion to newer formats (for example expanded RBA/LRSN related changes on older upgrade paths). DSNTIJNF appears in new-function mode activation stories on pre–function level release models and can have data sharing SCA rebuild implications—read the job prolog carefully. DSNTIJPM belongs with premigration readiness on the release you are leaving. Members such as DSNTIJXA, DSNTIJXB, DSNTIJCC, DSNTIJDG, and DSNTIJOS may be tailored for specific optional or site paths; always open the member and follow the Installation Guide table of steps for your exact version rather than memorizing every suffix in isolation.

Reading return codes and restarting safely

Expect a mix of RC=0 and carefully interpreted RC=4 on some catalog or verification steps, depending on release and whether objects already exist. Never assume RC=4 is harmless without reading the job’s SYSPRINT and IBM’s notes for that step. If a mid-stream job fails, fix the cause, then resume from the failed step—rewinding to DSNTIJIN after a successful catalog tailor can create messy duplicate-definition errors.

Keep a simple spreadsheet of job name, submit time, return code, and operator notes. Install weekends go smoother when the next shift can see what already ran.

Operational tips

• Submit in IBM’s documented order; capture return codes in the change record.
• Review JOB cards, accounting, and JCLLIB before the first submit.
• Keep the OUTPUT defaults member that produced the jobs for auditability.
• After start, run installation verification programs (IVPs) your site requires.
• For data sharing, expect per-member parameter jobs and shared catalog caution.

Explain It Like I'm Five

The panels were the shopping list. The DSNTIJxx jobs are the actual building steps: pour the foundation (data sets), write the house rules (ZPARMs), put the address on the map (DSNTIJMV), unlock the dictionary (catalog job), put tools in the drawers (DSNTIJSG and routines), then take a photo of the finished clubhouse (image copy) so you can rebuild it if something breaks.

Exercises

1. Match DSNTIJIN, DSNTIJUZ, and DSNTIJMV to one sentence each describing their job.
2. Why would DSNTIJRT fail if WLM environments from DSNTIJRW were never defined?
3. When should you run DSNTIJIC relative to DSNTIJTC?
4. Explain why data sharing members each need their own DSNTIJUZ.
5. Open a tailored job prolog in your lab and list three site-specific values it contains.