This section describes administration tasks such as signing on to the administration subsystem, using the System Administration Menu, and starting and stopping the administration subsystem.
The administration subsystem provides you with an interactive interface for configuring, controlling, and monitoring CallPath/CICS. You can sign on to it from any CICS terminal. You need to use transaction EQAC to query messages written to the CallPath/CICS message file. Alternatively, if you are logging the message data to a transient data queue, you could use an MVS facility such as IBM SDSF to access the data from TSO. Messages issued during initialization are always sent to the VSAM message file, therefore these files cannot be eliminated from the installation jobs, even if LOG=N is specified as an SCT option. (See "Task 6: Creating the System Configuration Table (SCT)".)
To sign on to the administration subsystem, enter EQAC on a blank CICS panel.
When you sign on to the administration subsystem, you see the System Administration Menu, Figure 7. You can do the following from the System Administration Menu:
You can start the administration subsystem manually, or it can be started automatically by the CICS startup routine. The administration subsystem must be running before any applications can communicate with CallPath/CICS.
You can start and stop communications with any of the defined switches. You can do this manually, or you can choose automatic startup and shutdown.
You can display the current status of the administration subsystem and communications with each switch.
For each defined switch you need to provide further configuration information. You can enter, display, and modify this information.
You can display and print error and information messages logged by CallPath/CICS during a time period you specify, if you are logging the CallPath/CICS messages to the VSAM files EQZLOGx. There is no facility provided by CallPath/CICS to display messages when they have been written to transient data. The displaying and archiving of this data when written to transient data is your responsibility. You should consider doing this to aid the IBM support group in debugging any CallPath/CICS problems.
When you display messages, you can also specify a switch and an application program. Only those messages associated with the switch and application program are displayed.
Log files are maintained for system messages, trace information, and message traffic counts. You can switch writing log records from a current log file to an alternative log file, so you can free a currently active log file for analysis at any time.
You can display counts of outgoing messages from the host to CallPath SwitchServer/2, incoming messages to the host from CallPath SwitchServer/2, and CallPath SwitchServer/2 messages between host and switch.
You can start and stop diagnostic tracing for any modules you select. You need to switch on diagnostic tracing only when you are asked to do so by your service representative.
You can start and stop performance tracing for any modules you select. Use the trace records to analyze the performance of your system.
Figure 7. System Administration Menu Panel
EQZMA01 System Administration Menu
Select one of the following options by typing its number.
Then press Enter.
_ 1. Subsystem startup/shutdown
2. Switch communications startup/shutdown
3. System status information
4. Switch description configuration
5. System messages
6. Log file control
7. Message traffic statistics
8. Diagnostic trace control
9. Performance trace control
IBM CallPath for OS/390
5655-B34 (C) Copyright by IBM Corp. 1991, 1999. All rights reserved.
Licensed Materials - Property of IBM.
US Government Users Restricted Rights - Use, duplication or disclosure
restricted by GSA ADP Schedule Contract with IBM Corp.
IBM is a registered trademark of International Business Machines Corporation.
F1=Help F3=Exit F11=Panel ID F12=Cancel
|
To select an option from the menu, type its number in the entry field. Then press Enter. The entry field is marked with an underscore character ( _ ). The cursor is already in this field. You need to move the cursor only if you want to see online help about the panel or one of the menu options.
To exit from the System Administration Menu and return to CICS, press F3.
You can use the administration subsystem panels
to make selections and enter choices.
Table 8 shows you what to do when a panel contains a
single entry field (indicated by
an underscore character) or multiple
entry fields indicated either by underscore characters or dots.
| Entry Field | What to Enter |
|---|---|
| Type one character in the entry field. |
| Type one character in one or more of the entry fields. You can type a different selection character in each field. Your requests are processed in the order they appear in the list. |
|
Type a selection character in one of the fields.
|
Press F1 at any time to get help. The kind of help you see depends on where you placed the cursor before you requested help. If the cursor is on a menu option, on a message, or in an entry field, the help will specifically relate to that menu option, message, or field. Otherwise, you see general help information about the panel. To end help, either press F3 or repeatedly press F12 to back out of one or more help panels.
Here is a description of each type of help:
Explains how to use the panel from which you requested help.
To see extended help:
Shows you what to type in an entry field or gives you information about a menu option.
To see contextual help, place the cursor either in an entry field or on a menu option. Then press F1.
Displays a list of the function keys that you can use and describes their assigned functions. To see keys help, press F9 from within a help panel.
Displays information about some of the action or warning messages that you see when you perform tasks using the administration panels. These messages have an A or a W as the last character of the message identifier. No help is provided for messages whose last character is an I as these messages provide information only. To see message help, place the cursor on the message. Then press F1.
Note: For more information about the messages in the System Messages log, refer to Appendix A, "System Messages".
Press F1 from any help panel to see how to use online help.
The administration subsystem panels use these function
keys:
Table 9. Administration Subsystem Function Keys
Active keys are listed at the bottom of the current panel.
The administration subsystem initializes some of the internal system tables and logs all messages generated by CallPath/CICS. Program calls from CallPath/CICS applications cannot be processed until the administration subsystem is started.
Your system can be set up so that the administration subsystem is started or stopped automatically by CICS (see "Task 2: Customizing CICS Macro Table Entries"), and you can start and stop the administration subsystem manually at any time using the administration panels.
To start and stop the administration subsystem manually:
You see the Subsystem Startup/Shutdown panel.
When you stop the administration subsystem, all switch communications are also stopped.
If you are not sure whether the administration subsystem is already running, press F6 to display the System Status Information panel. This tells you whether the administration subsystem is active or inactive, and also gives the status of switch communications. For more information about the System Status Information panel, see Chapter 6, "Monitoring Your System".
To return to the System Administration Menu, press F3.
The following sections contain detailed instructions for administration tasks.
You normally assemble the SCT when the system is installed; this process is described in "Task 6: Creating the System Configuration Table (SCT)". However, you can update the SCT at subsystem startup by using the EQZIN DD statement to read SCT overrides from a transient data queue. The EQZIN DD statement is not mandatory, and CallPath/CICS can operate with no overrides, but, if a dummy statement is not included, the message EQZ0384W SUBSYTEM STARTUP COULD NOT PROCESS SCT OVERRIDES is issued. See "Optional SCT Overrides".
Figure 8. Examples of SCT overrides
TOTALSTG=16000 MAXMSGS=999 QCLNTIME=4000 EQSWITCH PRIMARY=0008 SECONDARY=0002 EQPHONE PRIMARY=0020 SECONDARY=0008 EQCALLPR PRIMARY=0050 SECONDARY=0022 EQREG PRIMARY=0016 SECONDARY=0008 EQMON PRIMARY=0020 SECONDARY=0008 LOG=Y TD=Y LOGW=Y LOGI=Y LOGA=Y LOGU=Y DESTIDW=CSSL DESTIDI=CSSL DESTIDU=CSSL DESTIDA=CSSL |
Transaction EQDA (see "Diagnostic Aids") can be used to monitor CallPath/CICS system activity and this data, with data from the CallPath/CICS message log, can be used to improve system performance with regard to storage use within the CallPath/CICS subsystem.
Option 4 of transaction EQDA shows the primary and secondary space information used for various tables within the CallPath/CICS system. The number of extents used within the tables is also shown. The extent information could be used to tune the initial storage allocation for a table. After CallPath/CICS has been running for a while, you might see, using option 5 of transaction EQAC, a number of EQZ0342I messages in the CallPath/CICS message log. Associated with these messages is a table name such as EQAMQ or EQPHONE. These messages indicate that the primary space allocation specified for one of these tables has been exhausted and that more storage is required by the system to service application requests. Requests for more storage are handled asynchronously and so sometimes data can be lost if these requests are being held up in the CICS system.
For example, consider an application that issued a lot of STLREG calls at start up. The default allocation for the Register Ownership table is 16KB with a secondary allocation of 8KB. If the application issues 1000 STLREG calls within seconds, you might not be able to satisfy all of the requests, because of the way that CallPath/CICS handles requests for additional storage. If you look in the CallPath/CICS message log, you would see that there was a problem at startup. You would also see how many requests for more storage had been received for the EQREG table. You would be able to change the primary allocation for the STLREG table to satisfy all the requests, and eliminate problems on subsequent starts.
If, for example, the number of storage requests for table EQREG was 8, that would indicate that the register ownership table required 16KB + ( 8 * 8KB), that is 80KB, to satisfy the application request for that CallPath/CICS resource. If this consistently happened when CallPath/CICS was running, an override could be introduced so that secondary allocations might be minimized. For example:
//EQZIN DD * EQREG PRIMARY=0080 SECONDARY=0020 /*
The actual values you set for PRIMARY and SECONDARY will depend on your system.
| Note: | You are advised not to use overrides until either you are experiencing problems or you fully understand how CallPath/CICS manages storage use. |
The tables for which the primary and secondary space allocations can be changed are:
Space allocations are done on a global basis for a table. So if the space allocations are changed for this table then the space allocation for EQREQA and EQREQB will be the same even if switch 'B' is little used and switch 'A' is very active. So caution should be used if the default allocations are changed. The extent count as displayed by transaction EQDA is for the entire system whereas the actual number of extents per switch can be obtained from the CallPath/CICS message log.
Caution should be used overriding the default storage allocations and extreme care should be used so that any storage allocated by the overrides does not approach the value specified by the TOTALSTG parameter.
The other SCT parameters that can be overridden are:
The TOTALSTG parameter is described in "Task 6: Creating the System Configuration Table (SCT)". CallPath/CICS uses this parameter to control the amount of storage that CallPath/CICS uses within the CICS system. CallPath/CICS allocates storage as and when it requires it and it will allocate an amount for its use up to the amount specified by the TOTALSTG parameter. The amount being used by CallPath/CICS at any one time can be found by using option 4 of transaction EQDA. If the amount of storage used by CallPath/CICS approaches the value specified by the TOTALSTG parameter, you can increase TOTALSTG when the system is restarted by specifying a value such as TOTALSTG=16000 as an SCT override. Specifying TOTALSTG=16000 does not allocate a storage area of 16000KB bytes but it does allow CallPath/CICS to use up to 16000KB bytes of storage whilst executing.
The MAXMSGS and QCLNTIME parameters are described in "Task 6: Creating the System Configuration Table (SCT)". They can be entered as indicated in the figure above or as separate overrides such as:
//EQZIN DD * MAXMSGS=2000 QCLNTIME=60 /*
These parameters are described in "Task 6: Creating the System Configuration Table (SCT)".
