Space announcements

   

This space provides the same content as before, but the organization of the home page has changed. The content is now organized based on logical branches instead of legacy book titles. We hope that the new structure will help you quickly find the content that you need.

WORKID statement

The WORKID statement specifies a unique identifier for a unit of work performed within Log Master. Log Master keeps track of all job steps and actions using a combination of a job’s user ID and the work ID defined in this statement.

BMC strongly recommends that you define different jobs with a unique combination of user ID and work ID, particularly if you run multiple jobs concurrently or if you define any jobs as ongoing processes.

WORKID statement syntax diagram
OptionDescription

userID.

Specifies an identifier representing the user or entity that started the current job. A user ID can be up to eight characters long. The default value of this keyword is your TSO prefix or TSO user ID. Separate the user ID from the work ID with a period.

workID

Specifies an identifier that Log Master associates with all work performed in the current job or job step. The following rules apply to work IDs:

  • The name can be up to eighteen characters long.

  • The first character must be an alphabetic or national ($#@) character.

  • Subsequent characters can be alphabetic, numeric, or national characters.

The Log Master online interface assigns a default work ID name that contains the following sequence of information: a user ID, period, the character string $$WORKID, a four-digit sequence number. For example:

 RDAUSER.$$WORKID0001

The default work ID name is reserved for use by Log Master. You cannot create a work ID name that begins with the characters $$WORKID.

DESC 'description'

Specifies up to 64 characters of comments that you can associate with the current work ID.


Was this page helpful? Yes No Submitting... Thank you

Comments