The following primary commands may be used on the Archive Tracking Entries panel. Enter primary commands in the Command field.
Merges two or more existing archives into one new archive.
The MERGE command lists all available archive entries. Select up to 255 entries for merging by placing an S in the prefix area next to each entry. After selecting the entries, press PF3 to continue with the request or enter the CANCEL command to cancel it.
If you press PF3, the Merge Archive Submit panel appears. Use this panel to complete the request. The panel prompts you for this information about the merged archive:
Press PF3 to submit the merge job or enter the CANCEL command to cancel it.
Refreshes the entries on the panel so that you can view any new archives that were created since the session began. When you issue the REFRESH command, the entries return to their default sort order.
Sorts the entries according to the value of colname. Values for colname are:
You must specify at least one column name. You can specify more than one value at a time. For example, suppose you specify this command:
SORT SUBSYS FIRST
As a result, CA OPS/MVS sorts the entries first by the name of the CA OPS/MVS subsystem from which the archives were taken, and then by the dates and times of the first events in the archive data sets.
Point-and-shoot is enabled to SORT the archive tracking table using any column heading. To SORT the archive tracking table using the point-and-shoot method, place the cursor on the bottom line of a column heading and press Enter.
Use OPSVIEW option 7.1.5 to merge live OPSLOG data from multiple systems. You specify the systems, date and time ranges, the log that contains the merged data, the merge method, the work dataset prefix, the allocation parameters, the reset value, the create value, the save data value, the timeout, and the filter to apply to the data. Then, you invoke the merge and access the merged data.
Note: The OPSLOG merge function requires the CA OPS/MVS MSF facility and MSF license.
Follow these steps:
On the Merge OPSLOG panel, identify the systems from which you want to merge live OPSLOG data. A list of available systems appears at the bottom of the panel. The list includes the local system and remote systems with active MSF connections. You can select one or more systems to extract live OPSLOG data from the specified systems.
When you select a system, the Action field for the system displays *selected*.
On the Merge OPSLOG panel, identify the date and time range for the merge by specifying a start and end date and time. Live OPSLOG data from the specified time range extracts from the selected systems.
Note: Dates are YYYY/ MM/ DD format. Times are HH:MM format. The end date and time must be later than the start date and time. Data is collected from the zero second of the start time to the zero second of the end time non-inclusive. For example, if the start time is 10:01 and the end time is 10:02, data is collected from 10:01:00 to 10:01:59. Merge requests that include systems in different time zones are normalized to the time zone of the requesting system. Merge requests for a date/time range that crosses a daylight savings time boundary relative to the current time are not adjusted for daylight savings time and can yield unpredictable results.
On the Merge OPSLOG panel, identify the log to contain the merged data by specifying the name of an OPSLOG. Live OPSLOG data from the selected systems is loaded into the specified log.
To select the log to contain the merged data, specify the name of an OPSLOG on the Merged OPSLOG name field. The OPSLOG must be read-only, activated, and it cannot be the live OPSLOG. The log can be an in-storage log or an OPSLOG DIV dataset. The default name is MERGE#userid, where userid is the TSO users logon id. If the specified log does not exist, a new in-storage log is created automatically if the Create parameter is set to Y.
To see a list of OPSLOGs already defined, specify a ? in the Merged OPSLOG name field. The ? invokes the OPSLOG Selection List panel. The selection panel also lets you select an OPSLOG from the list for use in the merge. See Access OPSLOG Definitions (Option 4.13). Each instance of CA OPS/MVS has a limit of 32 defined OPSLOGs.
If *NONE* is specified for the log name, the records are sorted into a merge dataset, but not loaded into an OPSLOG. This sort is most useful in conjunction with the Save Data parameter. With Save Data specified as Y and a log name of *NONE* you can create and save a dataset of merged records without loading them into an OPSLOG. The merged data is preserved in the dataset and can be loaded/processed later.
On the Merge OPSLOG panel, identify the execution process for the OPSLOG data extraction by specifying the merge method. Live OPSLOG data is extracted from the selected systems using the specified method.
To select a merge method, specify the method on the Method field. You have the following available options:
Performs the OPSLOG data extraction process in an OSF server on the selected systems.
Performs the OPSLOG data extraction process using a started task (STC) on the selected systems.
When you select this method, you must also specify the name of the started task to execute on the selected systems.
To select the started task, specify the started task name on the STCname field.
Note: For more information about providing and configuring a started task to be used for the OPSLOG merge process, see Choose and Configure a Merge Method in the Administration Guide.
On the Merge OPSLOG panel, identify the work dataset name prefix that you want to use for allocating all work datasets. Work datasets include the extract datasets, sort message and control datasets, and the sortout/merge dataset.
Also, optionally specify any additional allocation parameters that you want to use for allocating the extract datasets on the selected systems. An extract dataset is allocated on each selected system using the specified parameters. Live OPSLOG data is extracted into the dataset. The requesting system sorts the records from all the extract datasets into a local merge dataset, and then loads the records from the merge dataset into the specified local OPSLOG. Once the data is loaded into the local OPSLOG, all work datasets are deleted except for the merge dataset. If Save Data is Y, the merge dataset is saved. If Save Data is N, the merge dataset is deleted.
The extract datasets are allocated with a name in the format below. The additional qualifiers are automatically appended to the specified dataset name prefix.
dsnpref.osmfidx.tarsys.tarsub
Specified dataset name prefix. The prefix allows up to 17 characters and the prefix conforms to standard dataset naming conventions of up to 8 characters per qualifier.
Specifies the origin (requesting) system smfid and the fourth character of the origin system CA OPS/MVS subsystem identifier (represented by x).
Request number in format Rnnn. The nnn indicates the 1-34 digit internal request number.
Specifies the target (selected) system sysname.
Specifies the target (selected) system CA OPS/MVS subsystem.
The extract datasets are allocated with the following allocation values in addition to what is specified on the Allocation parms field:
CA OPS/MVS calculates the space that is required for the allocation automatically based on the number of records that are extracted on each selected system.
The following additional allocation parameters are available for specification on the panel: UNIT, VOLUME, STORCLAS, MGMTCLAS, and DATACLAS. The syntax follows the convention for ADDRESS OPSDYNAM and TSO ALLOCATE. The smallest abbreviations are UNI, VO, ST, MG, and DATAC respectively.
The combination of allocation parameters must result in the extract datasets being allocated on DASD shared by both the requesting (origin) system and the selected (target) system. The selected system writes extracted live OPSLOG data to the dataset. The local system reads the dataset to load the OPSLOG data into the specified local merge OPSLOG.
Note: For more information about configuring all work datasets, see Verify the Allocation and Security Settings for Work Datasets in the Administration Guide.
On the Merge OPSLOG panel, the Reset value determines whether or not an existing, non-empty specified log is reset before loading merged records. If Reset is Y and the specified log is non-empty, the log resets prior to the load of merged records. Pre-existing records in the log are lost. If Reset is N and the specified log is non-empty, the merge is not performed and the specified log remains untouched. This parameter helps prevent the accidental overwrite of existing log data.
On the Merge OPSLOG panel, the Create value determines whether not a new, in-storage log of maximum size created automatically if the specified log does not exist. If Create is Y, a new log is created automatically using the specified name. If Create is N, a new log is not created automatically and the name of an existing log must be specified.
On the Merge OPSLOG panel, the Save Data value determines whether or not the merge dataset is deleted after the merged records are loaded into the OPSLOG. If Save Data is Y, the merge dataset is saved. This save allows the merge data to be preserved and loaded/processed another time using the OPSLOG Load OPSVIEW panel (option 7.1.6). The name of the merged dataset is provided in an output message. If Save Data is N, the merge dataset is deleted after the load.
The format of the merged dataset is:
dsnpref.OPLGMG.osmfidx.reqnum.OUTn – merge dataset (sort output dataset)
The n in OUTn indicates a number from 0-9. This number is appended automatically to minimize possible name conflicts with previously saved merged datasets. If all 10 possible datasets for a given dsnpref and request number combination already exist, the merge fails. Output messages are issued indicating that a merge dataset was not available. In this case, retry the merge to get a different request number or to specify a different prefix.
Refer to Step 6 for an explanation of the other qualifiers.
On the Merge OPSLOG panel, the Timeout value determines the maximum time to wait for all selected systems to respond to the merge request. Specify a value between 30 and 600 seconds. If the timeout value expires before all selected systems have responded, the merge only contains those systems that responded before the timeout.
On the Merge OPSLOG panel, the Filter parameter specifies the id/name of a previously created merge filter to apply to the data during extraction. Use of a merge filter is optional. When a merge filter is applied during a merge, only OPSLOG records matching the merge filter criteria are extracted and collected from the selected systems.
To create or update a merge filter and provide filter criteria, access the Access and Use the OPSLOG Merge Filter panel.
To see and choose from a list of existing filters, specify a ? on the Filter field.
On the Merge OPSLOG panel, you invoke the merge of live OPSLOG data with the MERGE or GO command.
To merge live OPSLOG data from the selected systems for the specified date and time range, type MERGE or GO on the panel Command line and hit enter.
Once the merge has completed, the OPSLOG data from the selected systems is available in the OPSLOG that was specified on the Log name field.
OPSLOG data for a selected system is not included in the merged data in the following cases:
If the OPSLOG to which the data is being loaded becomes full, the OPSLOG data wraps.
Informational and error messages that are associated with merge processing display automatically in a separate panel after the merge is invoked.
Lastmins specifies the last number of minutes that are taken from the present. Lastmins overrides any start time and end time that may exist if it has a value other than zero.
Valid Values: 1 through 720.
When you set to yes, CA OPS/MVS selects all MSF systems automatically in the same sysplex. Once selected, you can add more systems, or you can unselect certain systems from the list.
Since the merged OPSLOG data resides in an OPSLOG dataset, existing OPSLOG functions and utilities are available for use with the merged OPSLOG data.
For example, the OPSLOG that contains the merged data can be browsed with OPSLOG Browse, profiled, accessed with the OPSLOG built-in function, and viewed with OPSLOG Webview.
Additionally, the BRLOG command can be used on the OPSLOG Merge Panel to invoke OPSLOG Browse:
Invokes OPSLOG Browse for the merged OPSLOG specified in the Merged opslog name field.
To merge live OPSLOG data from multiple systems, use the Merge OPSLOG panel. To access the panel, you can either:
A display similar to the following example appears:
SY01 --- OPSLOG Merge Panel ---------------------- OPSA ------- Row 1 to 1 of 1 Command ===> Scroll ===> PAGE Specify input fields, time criteria, method and system selection then type GO to process or PF3 to EXIT. Filter:________ Merged opslog name ===> MERGED#USERID1 Reset: N Create: N Work DSNAME Prefix ===> USERID1 Save Data: N Allocation parms ===> Time Criteria: Extract Method: YYYY MM DD HH:MM Method ===> OSF (OSF,STC) Start ===> 2014/04/21 14:21 STCname ===> ________ End ===> 2014/04/21 14:22 Timeout ===> 60 System Selection Criteria: Specify S to select the desired systems for Opslog extraction or U to unselect systems.
Sel Ident Loc Plexname Smfid Subsys Action DDMMM HH:MM _ OPSDNM1 LOCAL PLEXC1 SY01 OPSA 21APR 10:31
******************************** Bottom of data ********************************
To create a new merge filter or update an existing merge filter, use the OPSLOG Merge Filter panel. To access the panel, type FILTER on the command line of the OPSLOG merge panel and hit enter.
The first level OPSLOG Merge Filter panel provides the following parameters:
The second level OPSLOG Merge Filter panel provides the following parameters:
When you access the OPSLOG Merge Filter, a display of the first level panel similar to the following example appears:
---------------------------- OPSLOG Merge Filter -------------------------------- Command ===> ____________________________________________________________________ Filter ID: TESTJB_ ( ? for list ) Active ID -TESTJB Specify I for Include (DEFAULT) and X for eXclude Jobname I ===> TEST*____ I ===> __________ I ===> __________ I ===> _________ I ===> __________ I ===> __________ I ===> __________ I ===> _________ MSGID I ===> __________ I ===> __________ I ===> __________ I ===> _________ I ===> __________ I ===> __________ I ===> __________ I ===> _________ Ruleset I ===> __________ I ===> __________ I ===> __________ I ===> _________ Color I ===> __________ I ===> __________ I ===> __________ I ===> _________ User I ===> __________ I ===> __________ I ===> __________ I ===> _________
Event Filters - specify Y or N MSG => Y CMD => Y DIS => Y DOM => Y ENA => Y EOM => Y GLV => Y OMG => Y REQ => Y SEC => Y TOD => Y SCR => Y ARM => Y EOS => Y EOJ => Y TLM => Y USS => Y API => Y RULETRACE => Y
------------------------------------------------------------------- | No level 2 filter - SCROLL DOWN for level 2 filter entry | ------------------------------------------------------------------- Press ENTER key to update filter. Enter END command to return to MERGE.
Scroll down to access the second level panel. A display similar to the following example appears:
---------------------------- OPSLOG Merge Filter -------------------------------- Command ===> ____________________________________________________________________ NOTE: Any non-blank entry in this second level filter will result in additional processing and may cause some delay in your MERGE extract. |--------------------------------------------------------------------------| | Scan for TEXT | Scan columns | | TEXT is case sensitive | FROM | TO | |-----------------------------------------------------|---------|----------| | ___________________________________________________ |________ |_________ | | ___________________________________________________ |________ |_________ | | ___________________________________________________ |________ |_________ | |-----------------------------------------------------|---------|----------|
ASID ===> ______ ===> ______ ===> ______ ===> ______
EXIT Type ===> ______ ===> ______ ===> ______ Valid Exit Types: MVS, JES3, IMS, OMG, DSN, TRAC, NIP, CICS, CNSV, CA7, and NONE
Press ENTER key to update filter. Enter END command to exit.
Use of the OPSLOG Merge Filter panels to create a merge filter is similar to the use of OPSLOG Browse Profile panels to create a browse profile. Refer to the OPSLOG profile sections listed below when using the OPSLOG Merge Filter panels. Note the Differences in Using the OPSLOG Merge Filter and OPSLOG Browse Profile Panels.
The following list describes the differences in using the OPSLOG merge filter and OPSLOG browse profile panels:
Use OPSVIEW option 7.1.6 to load saved merged OPSLOG data into an OPSLOG dataset. You specify the saved merge dataset containing the sorted, merged OPSLOG records, and the OPSLOG dataset into which the records are loaded. Then, you invoke the load and access the loaded data.
Follow these steps:
On the OPSLOG Load panel, identify the merge dataset that contains the sorted merged OPSLOG records to load into a local OPSLOG.
Merge datasets are created during the merge process that the OPSLOG Merge panel (Option 7.1.5) invokes. When you set Save Data to Y on the merge panel, the merge dataset is saved and can be loaded into a local OPSLOG using the OPSLOG Load panel. The name of the saved merge dataset is provided in the output panel for the merge at the end of the merge process.
To identify a saved merged dataset, specify the full name of the dataset in the Merged Dataset Name field or use a partial dataset name containing wildcard characters.
The wildcard characters are percent "%" for a single character match and an asterisk "*" for a multi-character match. A matching dataset list is displayed. Use the OPSLDS line command to select the desired dataset and hit PF3 to return to the 7.1.6 panel.
On the OPSLOG Load panel, identify the log to contain the merged data by specifying the name of an OPSLOG on the Merged Opslog Name field. The OPSLOG must be read-only, activated, and it cannot be the live OPSLOG. The log can be an in-storage log or an OPSLOG DIV dataset. The sorted merged data in the merge dataset is loaded into the specified log.
To select an existing OPSLOG, enter a question mark "?" in the name field and hit enter. A log name selection screen is displayed. Enter S to select a log and hit PF3 to the 7.1.6 panel.
After the load completes, the OPSLOG data from the merge dataset is available in the OPSLOG that was specified on the Merged Opslog Name field.
Since the merged OPSLOG data resides in an OPSLOG dataset, existing OPSLOG functions and utilities are available for use with the merged OPSLOG data.
For example, the OPSLOG that contains the merged data can be browsed with OPSLOG Browse, profiled, accessed with the OPSLOG built-in function, and viewed with OPSLOG Webview.
Additionally, you can use the BRLOG command on the OPSLOG Load Panel to invoke OPSLOG Browse:
Invokes OPSLOG Browse for the merged OPSLOG specified in the Merged Opslog Name field.
To load OPSLOG data from a saved merge dataset, use the OPSLOG Load panel. To access the panel, you can either:
A display similar to the following example appears:
SY01 ------------------------- OPSLOG Load Panel ------------ Subsystem OPSS Command ===>
Specify the saved merge dataset and the OPSLOG to contain the loaded records then type LOAD to process or PF3 to EXIT.
Merge Dataset Name ===> PUBLIC.OPLGMG.CA11V.R28.OUT0 (%,*) Merged Opslog Name ===> LOAD#USERID (?=Sel) Reset: N Create: N
|
Copyright © 2014 CA.
All rights reserved.
|
|