Five-Step z/VM Commands

Execution JCL › One-Step and Five-Step JCL › Five-Step z/VM Commands—Local Mode

Five-Step z/VM Commands—Local Mode

To specify that Culprit is executing in local mode, perform one of the following:

Link Culprit with an IDMSOPTI program that specifies local execution mode
Specify *LOCAL* as the first input parameter of the filename, type and mode identified by sysidms parm a in the CULPFD exec.
Modify the OSRUN statement:
```
OSRUN Culprit PARM='*LOCAL*'
```
Note: This option is valid only if the OSRUN command is issued from a System Product interpreter or an EXEC2 file.

Database Access

The following JCL modifications must be made in order to access non-SQL defined database records and tables:

If the CULP0 step is to be run locally, add the following commands for the CA IDMS/DB data dictionary and associated journal files:

FILEDEF dictdb DISK dictdb dictfile
FILEDEF j1jrnl DUMMY
FILEDEF j2jrnl DUMMY
          additional journal-file commands, as required

If the CULP2 step is to be run locally, add the following commands for the user's database and associated journal file:
```
FILEDEF userdb DISK user userdb
          additional database-file commands, as required
```
If a key file is to be used, add the following command in the CULP2 step:
```
FILEDEF SYS002 DISK keyfile FILE A3
```

Note: CA Culprit, CA IDMS/DB users who wish to override IDMSOPTI specifications at runtime can code either the LOCAL keyword or CVMACH= keyword expression on the DATABASE parameter, discussed in Chapter 11, DATABASE Parameter. For more information about IDMSOPTI, see CA IDMS System Operations Guide.

dictdb	DDname of the data dictionary DDLDML area
dictdb dictfile	Minidisk address of the database file (e.g., 500)
j1jrnl	DDname of the first disk journal file
j2jrnl	DDname of the second disk journal file
keyfile	Filename of the key file (required only if a key file is input)
userdb	DDname of the user database file
user userdb	Minidisk address of the user database file (e.g., 500)