Unlike APPC Transaction Programs and UNIX System Services (formerly Open Edition/MVS), which are relatively recent additions to the MVS family of supported address space types, System Address Spaces have existed since the inception of MVS. But SMF does not account for System Address Spaces in the same way it accounts for other address space types. Instead of the normal type 30 subtype 1-5 records generated for all other address spaces, SMF creates a unique record for System Address Spaces--the type 30 subtype 6 record. Prior to this product change NeuMICS discarded the SMF type 30 subtype 6 System Address Space records rather than processing them as a standard NeuMICS parallel step level file. This was done for a number of reasons:
- System Address Spaces are required by MVS and OS/390 and are generally considered overhead. There has never been a compelling need to provide chargeback accountability for these "background" tasks.
- System Address Spaces do not go through full function start. As a result, many of the metrics gathered for other address space types (such as EXCP I/O activity) are NOT collected and written to the System Address Space SMF type 30 subtype 6 records.
- The normal set of SMF records generated over the life cycle of a full function address space (such as the initiation, job end, and purge records) are not created for System Address Spaces.
- The SMF type 30 subtype 6 interval records written by SMF for System Address Spaces are cumulative, with each successive record containing resource usage to date, rather than true interval information. The NeuMICS program logic used to process other type 30 record subtypes does not support cumulative data.
- The SMF type 30 subtype 6 records for System Address Spaces contain none of the expected timestamp information other than the time the record was written to the SMF buffer. The lack of time/date fields such as Reader, Interval Start, Interval End, and Step Start, make analysis of the data difficult.
On the other hand, there are reasons to include system address spaces in the set of NeuMICS step level files:
- The NeuMICS MVS Hardware and SCP Analyzer (RMF) component reports on System Address Spaces. Processor workload utilization analysis and capacity studies that compare and or combine the RMF and SMF component files show disagreement in CPU utilization because of the lack of System Address Space activity on the SMF side.
- Started tasks may be initiated as System Address Spaces. That is, not all System Address Spaces are those required by MVS. These client created system address spaces may require accounting and chargeback as well as detailed analysis at the interval level of System Address Space activity on the SMF side.
- Clients periodically request this support. In the end, client requests were the driving force resulting in NeuMICS support for System Address Spaces. The following features are delivered with this product change.
NeuMICS System Address Space Support
- Two new files:
BAT_SA - System Address Space Activity File
BATSF6 - System Address Space Suspend File
The new step level file, (BAT_SA), is a parallel file to the BATPGM file and brings the total of different program types supported by the analyzer to six:
PGMTYPE FILE ------- -------------------------------------- The BAT_SA file is a true interval file. NeuMICS performs delta calculations on the cumulative type 30 subtype 6 interval records so that each BAT_SA file interval record contains only the resources consumed in that interval. Note that unlike the other step level files, which can contain either step (PGMINTVL='SE24') or interval (PGMINTVL='SE22','SE23') records, the BAT_SA file only contains interval records (PGMINTVL='SE26').
1 BATPGM - Batch User Program Activity
2 BAT_TS - SMF User TSO Activity
3 BAT_ST - System Task Program Activity
4 BAT_TP - APPC/MVS TP Activity
5 BAT_OE - Open Edition/MVS Program
6 BAT_SA - System Address Space Activity
The new suspend file (BATSF6) provides the means to perform delta calculations for System Address Spaces whose records are processed over multiple NeuMICS daily or incremental update runs. This NeuMICS internal file is not suitable for client reporting.
- New user input exit:
USRSST6 - Provides access to individual SMF type 30 subtype 6 records. This exit allows the deletion of specific System Address Space records (using the SKIP_REC data element).In addition, it provides client access to all data elements read from the type 30 subtype 6 and to the raw record itself.
The BAT_SA file output processing exit is the same as used for the other NeuMICS step level files. When PGMTYPE=6, the record is destined for the BAT_SA file. For additional information concerning these exits, refer to sharedprefix.MICS.SOURCE(#SMFEXIT) comments, and to the NeuMICS MVS Batch and Operations Analyzer guide, Sections 10.2.4 and 10.2.5.
- BATJOB file support
A new prefix.MICS.PARMS(SMFOPS) statement is available to control the summarization of BAT_SA step/interval level observations to the BATJOB file job level. The new statement
SAJOB - Summarize BAT_SA obs to the job level
NOSAJOB - Do not summarize BAT_SA obs to the job level
NOSAJOB is the default if no SAJOB/NOSAJOB statement is present in the SMFOPS member. This statement is fully described in the NeuMICS MVS Batch and Operations Analyzer guide, Section 126.96.36.199.
- Accounting support:
SMF6500 and the corequisite product change, ACT7000, provide NeuMICS Accounting and Chargeback product support for System Address Spaces.
After application of these product changes, System Address Space activity can be charged at either the step or job level using the same facilities currently in place for batch, TSO, started task, and APPC/MVS and UNIX System Services (formally known as Open Edition/MVS).
Note that a number of metrics present in other step level files (e.g., BATPGM, BAT_TS, etc.) are not present in the BAT_SA file, and therefore not available for chargeback purposes.
***************** IMPORTANT NOTE ********************* ** As part of the system modification steps for ** ACT7000, you are instructed to check your ** NeuMICS Accounting and Chargeback Rate Table ** Algorithm Qualifications to determine whether ** your selections will result in the automatic ** charging for System Address Space activity. ** Do the following: ** ** Enter MWF. ** ** Select options: * * ** 4-Management Support Applications (APPL) ** 2-Accounting and Chargeback ** 3-Parameter Specification and Generation ** 6-Rate Table ** (Under "Rate Table", select the unit(s) ** containing the NeuMICS MVS Batch and ** Operations Analyzer) ** ** If the ACTJBJ Batch Job Journal File is ** active, select it. ** ** 4-Algoritm Qualification ** ** Under "Algorithm Qualification", check the ** "Subsysid" value(s). If "*ALL" or "*DEF* ** is specified, you will charge for System ** Address Spaces at the job level. ** ** If the ACTJBP Batch Program Journal File is ** active, select it. ** ** 4-Algoritm Qualification ** ** Under "Algorithm Qualification", check the ** "Subsysid" value(s). If "*ALL" or "*DEF* ** is specified, you will charge for System ** Address Spaces at the step level. ** ** If neither the ACTJBP nor ACTJBJ journal ** file Algorithm Qualification "Subsysid" ** values contain "*ALL" or "*DEF", then you ** must insert a line with a Subsysid value of ** "@SAS" in order to charge for System Address ** Space Activity. You can charge for System ** Address Space activity from only one of these ** two journal files -- either ACTJBP or ACTJBJ. ** ** Note that "@SAS" is not recognized by MWF as a ** valid Subsysid value until ACT7000 is applied. ** ******************************************************
This product change corrects the following problems reported for the NeuMICS Batch and Operations Analyzer:
- When two jobs, or started tasks are received by JES within the same 1/100th of a second, they receive the same Reader Time Stamp (RDRTS). NeuMICS treats all jobs with an identical job name and RDRTS as a single job. The job level observation created from all steps and intervals of the multiple jobs are summarized together, and are assigned the JES Job Number (JESJOBNO) from one of the multiple jobs. Prior to this product change, all step and interval records from the multiple jobs were assigned the same single JESJOBNO value.
With this product change, the correct, original JESJOBNO is preserved in the step level observations for the individual steps and intervals. This allows, at the step level, a means to identify the individual jobs even though job name (JOB) and RDRTS are identical. (SMF6411,000033).
- The internal BATSFP01 suspend file for type 26 purge records is merged with currently input type 26 purge records during the DAY030 daily update step.