Screen processing


You can analyze and generate messages for z/OS and z/VM consoles. The screen processing algorithm is chosen based on the Console Type set on the Connection Info tab. z/OS screens are processed based on regular expressions that identify the first line of text in the message, the parts of the screen text that are added to the message as properties, and a WTORs. The z/VM console processing has additional functionality built in to manage the console states and allow unattended operation.

This feature works with the CCS Keyboard Lockout feature. When HOLDING or MORE appears at the bottom of the screen and the keyboard is unlocked, MVCA will automatically send the appropriate key strokes to clear the screen enabling keyboard lockout in the CCS session. This allows you to use the either the CCS viewer or the MVCA viewer. The z/VM console automatic page is enabled only when the console is in the following modes:

  • CP READ
  • VM READ
  • HOLDING
  • MORE

The automatic page is disabled in all other modes. When 'X E D I T', for example, is displayed on the last line, the automatic pager is disabled.

Note

Since the actual text of the status modes may be changed in the z/VM logo configuration file, it must be defined in the z/VM screen processing. The default values are the same as the defaults for z/VM.

Setting

Definition

Enable Pager

Enables the z/VM automatic pager. When the console status on the last line is MORE or HOLDING, MVCA will automatically clear the screen.

Note

The default setting is that the pager is enabled.

Pager Delay

The action of the automatic pager is delayed by the number of seconds specified here.

Running

The actual status indicator text on the last line for the Running mode. The default is RUNNING

CP Read

The actual text of the status indicator on the last line for the CP Read mode. The default is CP READ

VM Read

The actual text of the status indicator on the last line for the VM Read mode. The default is VM READ

Holding

The actual status indicator text on the last line for the Holding mode. The default is HOLDING

More

The actual status indicator text on the last line for the More mode.

 

GUID-D9D58491-5858-4F98-A093-E084B3C13375-low.png

This tab contains the following radio buttons:

  • Default setting
  • Custom setting

You select either the Default or Custom settings.

Default setting

When theDefault settings are used, the MVCA server will ignore any database settings and use the default parsing settings.

Custom settings

When the Custom settings are used, additional controls will appear depending on the console type (z/OS or z/VM).

The custom settings for the z/OS are listed below:

 

Setting

Definition

Scrolling Region Top

The line above the first message line. If the top line on the screen is a message line then this should be set to 0 which is the normal value for a z/OS console.

Scrolling Region Bottom

The last message line. For the typical model 2 z/OS console which is 24 lines this should be set to 20 so that the bottom 4 lines of status information and command input area will be ignored.

Skip Left Columns

Defines how many characters at the beginning of each line will be dropped when building multiple-line messages and by the RDL2 monitorMessage and autoClearMessage functions. For the typical z/OS console this should be set to 6.

Beginning of Message Pattern

The Automation server uses this to identify the beginning of a new message. The suggested default value of

^......[0-9][0-9]/.[0-9][0-9]/.[0-9][0-9].*

matches the time stamp that is normally included as part of z/OS console message output.

Message format is affected by the MFORM console setting. It is very strongly recommended that all z/OS consoles monitored by an Automation server have their MFORM set to T,S,J.

See Regular-Expressions for more information on the pattern syntax.

Event Header Pattern

Once a complete message has been identified this is used to extract parts of the message to set the value of variables named by the Event Header Token Names field. These variables may be used in RDL2 triggers that have been assigned to this session using the Automation server Rule-Assignments tab. The variables are also used to display Message Detail in the Automation viewer.

Event Header Token Names

Specifies the variable names to be set using the Event Header Pattern. The suggested default value of

TIME,SYSTEM,JOB,MSGID

should be used when the z/OS console conforms to our recommended format.

WTOR Header Pattern

Like the normal message pattern but identifies WTOR (write-to-operator-reply) messages that contain a reply number. The suggested default value of

^......(/d/d/./d/d/./d/d) +([^ ]+) (........) /*([0-9]+)[ ]*+([^ ]+).*

extracts five strings - the values within the 5 matching sets of left and right parentheses - to set the token names.

See Regular-Expressions for more information on the pattern syntax.

WTOR Header Token Names

Specifies the variable names to be set using the WTOR Header Pattern. The suggested default value of

TIME,SYSTEM,JOB,REPLYNUM,MSGID

should be used when the z/OS console conforms to our recommended format.

 

GUID-63E7014D-FA30-4201-ABF7-EF7D91D265FB-low.png

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*