Creating Encrypted Command File - zOS
Creating Encrypted Command File for z/OS
Command File
In this example, a Universal Command command file named MY.CLEAR.CMDFILE contains the following data:
Command File Options
The command file options used in this example are:
Option | Description |
User ID or account with which to execute the remote command. | |
Password associated with -userid. |
Note
If you are creating an encrypted file for use with the Universal Controller CLI (Command Line Interface), you must use the CLI command line switches to specify the user ID and password:
JCL
The following JCL encrypts the command file allocated to ddname UNVIN using AES encryption and an encryption key MYKEY123:
The resulting encrypted command file is written to ddname UNVOUT.
SYSIN Options
The SYSIN options used in this example are:
Option | Description |
Encryption key used by the encryption algorithm. | |
Specification for whether or not AES encryption is used. |
Contents of Encrypted File
The figure below illustrates the contents of MY.ENCRYPT.CMDFILE.
This encrypted command file can now be used by any Universal Agent command on any platform by specifying the encryption key MYKEY123.