The OPSSMF function enables AOF rules to create user-formatted SMF records or to write the product internal summary SMF records. You can use this function in the AOF Test Facility; if you do, OPS/REXX checks the syntax of the OPSSMF arguments and returns a value of zero without writing any SMF records. All the SMF records created by the product will use the SMF record number as specified in the SMFRECORDNUMBER product parameter. The various subtype record numbers can be used to identify the different record formats. Subtypes from 1 to 999 are reserved for the internally generated SMF records. Subtypes from 1000 to 32767 can be used for user-created SMF records.
This function has the following format:
var = OPSSMF(subtype{,data})
This argument is:
1, 4, 5, or 8, corresponding to one of the CA OPS/MVS summary SMF record numbers. In this case, the data argument must not be specified.
A numeric value between 1000 and 32767, representing the user subtype SMF record number. In this case the data argument must be specified.
The data argument is the part of the SMF record following the standard CA OPS/MVS 40-byte header section. This data can contain at most 344 bytes. If records exceed this limit, OPS/REXX truncates them and issues a warning message.
Example of OPSSMF
This example uses the OPSSMF function to create a subtype 1000 SMF record:
/* Assume that the record has been built in an OPS/REXX variable called smfrecord */ temp = OPSSMF(1000,smfrecord)
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |