Request unit formats for the performance monitor interface

This section describes the general format of the performance monitor CNM request units that are supported by the performance monitor interface. Only monitor applications can issue these CNM request units.

A typical request unit begins with the CNM request unit format described in Table 2 which contains a subtype code identifying the desired function, as follows:

Start Performance Data Collection (X'22')
Sent by the performance monitor to start the collection of performance data as specified in this CNM RU or to dynamically enable or disable SMF and blocked route data collection.
Stop Performance Data Collection (X'23')
Sent by the performance monitor to stop the collection of specified performance data that has been previously started via the Start Performance Data Collection CNM RU.
Stop All Performance Data Collection (X'24')
Sent by the performance monitor to stop all performance data collections that have been previously started via the Start Performance Data Collection CNM RU.
Collect Performance Data (X'25')
Sent by the performance monitor to retrieve performance data as specified in this CNM RU.

Following the subtype code byte are eleven reserved bytes.

For all the above RUs except Stop All Performance Data Collection (X'24'), the CNM request unit format and the reserved 11 bytes must be followed by a request packaged in the following manner:

The request code vector must be first, as shown in Table 1. It identifies both the categories of data and the set of resources targeted by the CNM RU. Specify one major category, one or more subcategories within that major category, and the desired resource, if applicable, that should be processed for the request.
The request code vector may be followed by a resource data description (presented in Table 2) that supplies the name for a resource that the request is targeting. It is comprised of a prefix vector and an identifier vector. The identifier vector is where the resource is actually named. The prefix vector provides necessary information about the identifier format or the resource itself.
Note: The prefix vector is a reserved field.

The resource data description must only be included when applicable, as indicated by the target resource set field in the request code vector.

There is a limit of one request per CNM RU, except for Collect Performance Data (X'25') RUs, where combining is allowed so long as none of the requests require a resource data description. When more than one request follows a CNM RU, the last request must be flagged.

Table 1. Request code vector format
Byte	Bit	Value	Description
00-01			Length of request code vector (including length field)
02-03			Request flags (common)
	01-14		Reserved
	15		Last request (Collect Performance Data subtype only)
		0	Yes
		1	No
04-05			Request flags (based on CNM RU subtype code)
	0-11		Reserved
			Start Performance Data Collection
	12		SMF data enablement
		1	Enable
		0	Disable
	13		SMF switching function indicator
		1	SMF switch requested
		0	SMF switch not requested
	14		Non-inactivation event enablement
		1	Enable
		0	Disable
	15		Non-inactivation event switching function indicator
		1	Non-inactivation event switch requested
		0	Non-inactivation event switch not requested
			Collect Performance Data
	12-14		Reserved
	15		Reset requested
		1	Yes
		0	No
			Stop Performance Data Collection
	12-15		Reserved
06-07			Reserved
08-09			Major category code
		X'0001'	VTAM® global data
		X'0002'	Virtual route data
		X'0003'	RTP connection data
		X'0004'	Application data
		X'0005'	Coupling facility structure data
10-11			Reserved
12-19			Subcategory code (based on specified major category code): Note: One or more valid subcategories can be specified.
			VTAM global data
	0		Environment data
	1		Installation-wide exit data
	2		Storage data
	3		Session data
	4		APPN directory services data
	5		APPN topology data
	6		CSM data
	7-63		Reserved
			Virtual route data
	0		Basic route data
	1-63		Reserved
			RTP connection data
	0		Basic RTP connection data
	1-63		Reserved
			MNPS data
	0		Basic application data
	1-63		Reserved
			MNPS coupling facility structure data
	0		Basic MNPS coupling facility data
	1-63		Reserved
20-23			Reserved
24			Target resource set (based on specified major category code):
			VTAM global data
			Reserved
			Virtual route data
		X'00'	Single virtual route—resource data description for single virtual route must be attached to request code vector
		X'80'	By destination subarea—resource data description for destination subarea must be attached to request code vector
		X'FF'	All routes
			RTP connection data
		X'80'	Destination CP name - resource data description for destination CP must be attached to request code vector
		X'FF'	All RTP connections (Note that this value is not valid for start performance data collection)
25-27			Reserved

Table 2. Format of all possible resource data descriptions
Byte	Bit	Value	Description
			Destination subarea: Prefix
00-01			Length of prefix including length field
02-03			Reserved
			Destination subarea: Identifier
00-01			Length of identifier including length field
02-m			Destination subarea number (EBCDIC, numeric only, leading zeroes allowed)
			Single virtual route: Prefix
00-01			Length of prefix including length field
02-03			Reserved
			Single virtual route: Identifier
00-01			Length of identifier including length field
02-03			Virtual route number (EBCDIC, numeric only, leading zero required)
04-m			Destination subarea number (EBCDIC, numeric only, leading zeroes allowed)
			Destination CP: Prefix
00-01			Length of prefix including length field
02-03			Reserved
			Destination CP: Identifier
00-01			Length of resource data including length field
02-09			Network ID (EBCDIC, left justified)
10-17			CP name (EBCDIC, left justified)