Ending one RKLVLOG and starting another

When you re-create a problem to send it to IBM® Software Support, you can close the current RKLVLOG spool dataset and open a new one.

Use the z/OS® MODIFY command to open a new problem. This command is issued from a z/OS console. The TLVLOG command manages the recording of information to RKLVLOG.
Keyword Description
Switch Is the keyword that dynamically allocates a new RKLVLOG file using the current values, begins recording on the new file, and closes the current RKLVLOG file, releasing it for processing by JES.
class Is the one-character JES SYSOUT class. CLASS=A is the TMS: Engine startup value.
copies Is the copy count. The valid range is 1-254. COPIES=1 is the startup value.
Note: JES2 allows 255, but JES3 allows only 254.
dest Is the 1-8 character JES SYSOUT destination. DEST=() is the startup value.
fcb Is the 1-4 character FCB name to be used. FCB=() is the startup value.
form Is the 1-4 character form name to be used. FORM=() is the startup value.
hold Determines whether the SYSOUT is to be placed in a JES operator hold when spun off. Specify YES (operator hold is requested) or NO. HOLD=NO is the startup value.
Note: If HOLD=YES is specified, you must issue the appropriate JES release command for the SYSOUT dataset to be processed by JES.
maxlines Is the maximum number of lines to be written to RKLVLOG, in thousands (for example, MAXLINES=2 means a maximum of 2000 lines). The valid range is 0 through 16000 (16 million lines). When this number is reached, an automatic TLVLOG SWITCH is performed, closing the current RKLVLOG and allocating a new one If the specified value is 0, there is no maximum; you must manually enter TLVLOG SWITCH to switch log files. MAXLINES=0 is the startup value.
Note: Unlike the other values, MAXLINES takes effect immediately. If the new MAXLINES value is less than the number of lines that have already been written to the current RKLVLOG, a switch is immediately performed.
ucs Specifies the 1 to 4 character UCS name to be used. UCS=() is the startup value.
user Is the 1-8 character user ID to which the SYSOUT is to be spooled. Ignored if DEST is blanks. USER=() is the startup value.
wtrname Is the 1-8 character external writer name to be used. WTRNAME=() is the startup value.

Usage Notes:

  • The TLVLOG command performs up to three functions, depending on the keywords that are specified. Assuming that you selected all three functions, they are performed in the following order:
    1. Updates the dynamic allocation values. With the exception of MAXLINES, these values are used when the next dynamic allocation is performed. Values are updated whenever they are coded on the command.
    2. Lists the current dynamic allocation values. This is always done.
    3. Switches RKLVLOGs. This is done only when SWITCH is specified on the command.
      Note: You may update values and request a switch with the same command; the values are updated first, then the switch is performed.
  • RKLVLOGs may be automatically closed after a certain number of records have been written to them, similar to the MVS SYSLOG processing. Refer to the MAXLINES keyword for more information.
  • To set up an automatic RKLVLOG switch whenever the TMS: Engine address space is started, add the following command to your RKANCMD startup CLIST:

    TLVLOG MAXLINES=nnn

    This command causes RKLVLOG to be automatically closed and released to JES whenever nnn thousands of lines have been written. If needed, you can add other installation-dependent values (for example, CLASS) to this command.

  • Many diagnostic messages are recorded in RKLVLOG. If you set RKLVLOG to spin off automatically, or if you explicitly switch RKLVLOG, you must ensure that the SYSOUT files are kept at least for the life of the TMS: Engine run, in case they are required for problem solving.
  • You might want to issue a TLVLOG SWITCH command after a problem occurs. This spins off the RKLVLOG data relating to the problem into a separate spool dataset, which can be included as part of the TMS: Engine standard problem documentation. Be sure to include all previously spun-off RKLVLOG files.
  • Because RKLVLOG is managed with standard IBM data management routines, records are buffered before being written. If you are viewing the currently active RKLVLOG with a product such as SDSF, you do not see the latest messages. Issue the command FLUSH TLVLOG to force the current data management buffer to be written. Do not use the TLVLOG SWITCH to spin off the current RKLVLOG for this purpose, as it unnecessarily fragments the messages recorded in RKLVLOG.
  • Unless you explicitly set a non-zero MAXLINES value, RKLVLOG never automatically switches.
  • If any error occurs when writing to RKLVLOG, TMS: Engine issues a message and disables RKLVLOG recording. However, messages continue to be written to VIEWLOG and to all active operator interfaces. Depending on the error, you may be able to restart RKLVLOG by issuing a switch request.

Here are some examples of ways to use this command:

  • To list the current RKLVLOG destination and values: tlvlog
  • To establish class X and destination SYSPROG as default SYSOUT attributes, and the maximum number of lines as 20,000: tlvlog class=x dest=sysprog maxlines=20
  • To switch to a new RKLVLOG: tlvlog switch