Move from the console tracking facility to the Generic Tracker

Description

Before z/OS V2R1, the console tracking facility was used to track use of system functions; however, it had some limitations. Starting with z/OS V2R1, the console tracking facility is being replaced with a new enhanced Generic Tracker. As of z/OS V2R1, support for the console tracking facility parmlib member, CNIDTRxx, is no longer provided. The Generic Tracker accepts GTZPRMxx parmlib members, and a tool to convert CNIDTRxx to the Generic Tracker GTZPRMxx is also provided.

Table 1 provides more details about this migration action. Use this information to plan your changes to the system.

Table 1. Information about this migration action
Element or feature: BCP
When change was introduced: z/OS V2R1.
Applies to migration from: z/OS V1R13.
Timing: Before the first IPL of z/OS V2R2.
Is the migration action required? Yes, if you have started or customized the console tracking facility.
Target system hardware requirements: None.
Target system software requirements: None.
Other system (coexistence or fallback) requirements: None.
Restrictions: None.
System impacts: It is assumed that the retired console tracking facility commands are typically issued manually and for diagnostic purposes only, not in any scripts or automation tools. The callable service CNZTRKR, compiled into executable programs, continues to be supported and the internal routing of any data passed to CNZTRKR and the Generic Tracker will be transparent to the existing CNZTRKR caller.
Related IBM Health Checker for z/OS check: None.

Steps to take

Follow these steps:
  • Replace the use of any console tracking facility commands. Use COMMNDxx, automation scripts, or manually enter the commands on the console command line with their corresponding Generic Tracker (GTZ) counterparts. You can use the following mapping as a quick reference:
    • Instead of using COMMNDxx to start the console tracking facility, use the new system parameter GTZ (in IEASYSxx) to specify a GTZPRMxx member that specifies the SETGTZ TRACKING=ON command.
    • Instead of the DISPLAY command, consider using utility GTZPRINT or a user-written program with the service GTZQUERY to retrieve, store, and process current tracking data.
    • Instead of SETCON TRACKING={ON|OFF}, use SETGTZ TRACKING={ON|OFF}
    • Instead of SETCON TRACKING=ONWITHABEND, use SETGTZ DEBUG(ACTION=ABEND...)
    • Instead of DISPLAY OPDATA,TRACKING, use DISPLAY GTZ command, the GTZPRINT tool, or the GTZQUERY macro service.
    • Instead of SET CNIDTR=xx, use SET GTZ=xx or system parameter GTZ in IEASYSxx
  • Instead of having any SETGTZ commands in COMMNDxx, consider putting them into GTZPRMxx parmlib members. You can use the SET GTZ command or the GTZ system parameter in IEASYSxx to select and execute the content of those GTZPRMxx.
  • For any new applications use macro GTZTRACK instead of macro CNZTRKR. Consider converting any existing use of CNZTRKTR to GTZTRACK.
  • Convert existing CNIDTRxx parmlib members to GTZPRMxx. See the sample GTZCNIDJ for how the GTZCNIDT conversion tool can help you automate this conversion.

Reference information

For more information, see the following references:
Parent topic: BCP actions to perform before the first IPL of z/OS V2R2