CRTPFRDTA (Create Performance Data)
CRTPFRDTA Command syntax diagram
Purpose
The Create Performance Data (CRTPFRDTA) command creates a set of performance database files from performance information stored in a management collection (*MGTCOL) object. See the topic performance database files and file fields for more information about these files.
Performance database files and file members will be created as needed based on the data contained in the management collection object and the information requested on this command. If database files already exist and the requested member exists in any of them, the member will be cleared before the collection is generated.
Required Parameters
- FROMMGTCOL
- Specifies the name of the management collection object from which a set of performance database files is to be created.
The possible library values are:
QPFRDATA: The data is located in the IBM-supplied performance data library, QPFRDATA.
library-name: Specify the name of the library for the management collection object.
from-management-collection-name: Specify the name of the management collection object that is to be used.
Single Value
*ACTIVE: The currently active collection object will be used. If *ACTIVE is specified, but no active collection is in progress, the command will end with escape message CPF0A1A.
Optional Parameters
- TOMBR
- Specifies the database file member name to which the output data is written. If a member by this name does not exist in each performance database file, one will be created with the specified name.
*FROMMGTCOL: The name of the management collection object is used as the performance database file member name.
to-member-name: Specify the name of the member to which the output should be written.
- TOLIB
- Specifies the library where the database files for performance data are to exist. Each file that is not found in the specified library is automatically created in that library.
*FROMMGTCOL: The performance database files are located or created in the same library as the management collection object (FROMMGTCOL parameter).
to-library-name: Specify the name of the library where the performance database files are located or should be created.
- TEXT
- Specifies the text that briefly describes the database member receiving the performance data. More information on this parameter is in Commonly used parameters.
Note: The specified text is used for each member across the set of performance database files associated with the collection. *SAME: If the member already exists, no change is made.
*FROMMGTCOL: Text associated with the management collection object is used as the member text.
*GEN: The following text will be generated - "Created from <collection name> in library <library name>". If the member already exists, no change is made.
*BLANK: Text is not specified.
'description': Specify no more than 50 characters of text, enclosed in apostrophes.
- CGY
- Specifies the categories in the management collection object which will be processed into database files.
*FROMMGTCOL: All of the categories present in the management collection object will be processed into database files.
category-name: Specify the name of the category of performance information to be processed from the management collection object. Multiple category names may be specified. Valid category names are:
- Name
- Description
- *APPN
- APPN
- *CMNBASE
- Communications (Base)
- *CMNSAP
- Communications (SAP)
- *CMNSTN
- Communications (Station)
- *DISK
- Disk
- *DOMINO
- Domino for iSeries >
- *HDWCFG
- Hardware configuration
- *HTTP
- HTTP Server (powered by Apache)>
- *IOPBASE
- IOP (Base)
- *IPCS
- Integrated xSeries Server>
- *JOBMI
- Jobs (task and thread data)
- *JOBOS
- Jobs (job data)
- *LCLRSP
- Local response time
- *POOL
- Pool
- *POOLTUNE
- Pool Tuning
- *SNADS
- SNADS
- *SUBSYSTEM
- Subsystem
- *SYSBUS
- System Bus
- *SYSCPU
- System CPU
- *SYSLVL
- System Level Data
- *TCPBASE
- TCP/IP (base)
- *TCPIFC
- TCP/IP (interface)
- *USRTNS
- User-defined transaction data>
- INTERVAL
- Specifies the time interval (in minutes) between successive entries in the database file(s). Within the database, these collection intervals will be identified by interval number and interval time.
Interval numbers will begin with 1 and increment with each interval. Interval time will be based on time at the end of the interval synchronized to the clock time (e.g. if INTERVAL(15) is specified, intervals could be generated as 01:00:00, 01:15:00, 01:30:00, and 01:45:00).
*FROMMGTCOL: The default collection interval from the management collection object will be used.
number-of-minutes: Specify an interval value ranging from 0.25 (15 seconds) through 60 minutes.
- FROMTIME
- Specifies the starting date and time of the performance data in the management collection object which will be used to create the performance database files. This time combined with the interval value will determine the date and time for each data base interval.
*FROMMGTCOL: The starting date and time is the date and time that the management collection object was created.
Element 1: Starting Date
starting-date: Specify the starting date for which collection data is generated. The date must be entered in the format specified by the system value QDATFMT and, if separators are used, as specified by the system value QDATSEP.
Element 2: Starting Time
starting-time: Specify the starting time on the specified starting date for generating the database intervals. The time is specified in 24-hour format with or without a time separator as follows:
- With a time separator, specify a string of 5 or 8 digits, where the time separator for the job separates the hours, minutes, and seconds. If you issue this command from the command line, the string must be enclosed in apostrophes. If a time separator other than the separator specified for your job is used, this command fails.
- Without a time separator, specify a string of 4 or 6 digits (hhmm or hhmmss) where hh = hours, mm = minutes, and ss = seconds. Valid values for hh range from 00 through 23. Valid values for mm and ss range from 00 through 59.
If the starting date is specified and the starting time is not, the starting time will default as follows:
- If the starting date specifies the first date of the collection, the starting time will be set to the start time of the collection.
- If the starting date does not specify the first date of the collection, the starting time will be set to midnight (00:00:00).
- TOTIME
- Specifies the date and time of the last performance data in the management collection object which will be used to create the performance database files.
*FROMMGTCOL: The date and time of the end of the collection in the management collection object will be the ending date and time for database generation.
*ACTIVE: The generation of the database will continue until the currently active collection ends.
This option causes the database to be generated concurrently with the active collection. The data base will be generated based on the start time specified for any data currently in the management collection object. Additional data will be processed as it is added to the collection object. This will continue until the current collection is ended or cycled.
Because this option can result in processing for a very long time, it is recommended that TOTIME(*ACTIVE) be specified only when running CRTPFRDTA in a batch job.
Element 1: Ending Date
ending-date: Specify the ending date for which data from the collection object is used to generate the database files. The date must be entered in the format specified by the system value QDATFMT and, if separators are used, as specified by the system value QDATSEP.
Element 2: Ending Time
ending-time: Specify the time for the specified ending date for which data from the collection object is used to generate the database files.
See the description of start-time for details about how time can be specified.
If the ending date is specified and the ending time is not, the ending time will default as follows:
- If the ending date specifies the last date of the collection, the ending time will be set to the ending time of the collection.
- If the ending date does not specify the last date of the collection, the ending time will be set to 23:59:59.
Examples for CRTPFRDTA
Example 1: Generating All Data
CRTPFRDTA FROMMGTCOL(Q099365001) TOMBR(JAN1) TOLIB(MYLIB)In this example, the database is generated for all categories contained within the management collection object Q099365001 in library QPFRDATA. The performance database files will be created into library MYLIB and the collection member name will be JAN1.
Data is generated from the start of data collection within this management collection object to the end of that collection. The database interval is the default collection interval that was specified at the time the collection was started.
Example 2: Selecting Specific Data
CRTPFRDTA FROMMGTCOL(Q099364002) TOMBR(JAN1J) TOLIB(MYLIB) CGY(*JOBMI) INTERVAL(15) FROMTIME(('01/01/98' '14:00:00')) TOTIME(('01/01/98' '16:00:00'))In this example, only the database file QAPMJOBMI is generated using *JOBMI category information from management collection Q099364002 in library QPFRDATA. The database interval will be 15 minutes even if the data was collected more frequently (for example, the management collection object may contain data collected every 5 minutes). The generated file will contain only data that was collected between 2:00 PM and 4:00 PM even though the collection object may contain data for a larger time interval.
Error messages for CRTPFRDTA
*ESCAPE Messages