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:

-userid T02JAH1 -pwd thames

Command File Options

The command file options used in this example are:

Option	Description
-userid	User ID or account with which to execute the remote command.
-pwd	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:

//UENCRYPT EXEC PGM=UENCRYPT
//STEPLIB  DD  DISP=SHR,DSN=UNV.SUNVLOAD
//SYSPRINT DD  SYSOUT=*
//SYSOUT   DD  SYSOUT=*
//CEEDUMP  DD  SYSOUT=*
//UNVIN    DD  DISP=SHR,MY.CLEAR.CMDFILE
//UNVOUT   DD  DISP=SHR,MY.ENCRYPT.CMDFILE
//SYSIN    DD  *
-key MYKEY123 -aes YES
/*

The resulting encrypted command file is written to ddname UNVOUT.

SYSIN Options

The SYSIN options used in this example are:

Option	Description
-key	Encryption key used by the encryption algorithm.
-aes	Specification for whether or not AES encryption is used.

Contents of Encrypted File

The figure below illustrates the contents of MY.ENCRYPT.CMDFILE.

# Universal Encrypt
#   Date . . . . . : Thu Nov  3 07:29:03 2011
#   User . . . . . : T02JAH1
#   Host . . . . . : hosta.acme.com
#   Program  . . . : uencrypt 3.2.0 Level 5 Release Build 130
#   Encryption . . : AES 256-bit

1F7DAF62583C813EA874CA168FF626C348F7BF171477D380D9A2FFFED33C539B71B4206EA5021F
D92CDFDD931C3B88B9CD711A4693EFE6B49FAE9431E9C946F7F35C9B4C31335BFB3F97F0686EFF
37068245A6B58CBFE2ADE32997A132C4114AC52CD615B2E7E8672ED0BF9867CA13B1

This encrypted command file can now be used by any Universal Agent command on any platform by specifying the encryption key MYKEY123.

Components

Universal Encrypt

Universal Agent 7.5.x

Creating Encrypted Command File - zOS