Unicenter Workload Control Center r1 SP4 Server Status Troubleshooting Guide
Table of Contents 1 Introduction 3 2 Information Page 3 3 Server Status Portlet 3 3.1 Configuration User Usage... 3 3.2 Troubleshooting Server Status... 4 3.2.1 Server Status Portlet Messages... 5 4 Verifying Server Status 7 4.1 JCC Messages... 7 4.1.1 CCI Link Messages... 8 4.1.2 Server Verification Messages... 10 5 Frequently Asked Questions 14 Page 2 of 15
1 Introduction The Information page, Server Status Portlet, Server Status page and CCI Links Status page help set up the configuration environment and verify the status of a Unicenter Workload Control Center (UWCC) server. This document guides you through the troubleshooting process of a server in UWCC r1 SP4. 2 Information The Information page displays information about the current status of the UWCC environment. The page provides tips for configuring a standard environment and enables you to determine potential configuration errors. This page is the first place to look for the status of your UWCC environment and determine whether there are any potential issues that will affect the environment. For example if you add a server but do not create a credential user for this server, this page will display a warning message. You can also use the Information page to get help for setting up your UWCC configuration. The help provides tips for configuring objects such as servers and users, and includes warnings about potential configuration errors. Note: You can keep the Information page open the entire time you work with Configuration Manager. Refresh the page each time you modify a parameter to ensure the page provides updates of potential issues. 3 Server Status Portlet The Server Status Portlet summarizes the status of all UWCC servers. This portlet uses the configuration details and the configured global user (configuration user), and the credential user(s) /credential group(s) of the servers to verify the server status. 3.1 Configuration User Usage In Unicenter Enterprise Job Manager (EJM) r1 SP3, the Server Status and Job Status Views portlets were introduced as part of the Job Command Center. Both portlets must connect to backend job management servers; a successful connection requires a valid user for the back-end job management server. In Unicenter EJM r1 SP3, the user for the connection was the Portal user. If the user had valid credentials either through the Portal ID and password, or through an associated credential user, the connection would be successful and the appropriate data returned. If the user did not have valid credentials for a particular back-end job management server, the server status would indicate that the connection to the server was down, and the Job Status View would indicate that the connection had failed. In Unicenter WCC r1 SP4, the ability to add a global user for the Server Status and Job Status Views portlets was added. The global user provides the ability to retrieve status information from the servers for all users, without providing any additional access. Table 1: Server Status Portlet Messages The following table summarizes the server status indicators and their related messages. Server Status Indicator Server Status (Displayed Message) active Global User not configured Page 3 of 15
Credential User not configured Unable to login to server. Invalid Credential User Unable to access server 3.2 Troubleshooting Server Status The following questions help you get started: Question Are you getting an error symbol as the Server Status Indicator for the server? Troubleshooting Steps 1. Refer to the Information Page: i. In Configuration: Setup: Servers, visit the Information page and review the tips and issues listed. ii. Also visit the Security tab on the Information page and review the tips and issues listed. iii. When you are finished, return to the Configuration Manager window to modify the configuration as necessary. iv. After the modification, deploy and restart the required services. Note: On the Deploy tab, you can use the Deploy Details: Undeployed Changes and Deploy Details: Existing Configuration pages to determine which configuration changes you must deploy, as well as which configuration changes have previously been deployed. The Services page indicates which services need to be restarted, if any, when configuration changes have occurred. 2. Verify Server Status: i. To help diagnose a server problem, visit the Verify Server Status page. To view a list of errors and alerts, enter the credentials and click Verify. ii. For an explanation of the error and alert messages and the required actions to help diagnose and rectify the problem, refer to the section JCC Messages. Are you getting a warning symbol the Server Status Indicator for the server? 1. Refer to the Information page: i. In Configuration: Setup: Servers, visit the Information page and review the tips and issues listed. ii. Also visit the Security tab on the Information page and review the tips and issues listed. iii. When you are finished, return to the Configuration Manager window to modify the configuration as necessary. iv. After the modification, deploy and restart the required services. Note: On the Deploy tab, you can use the Deploy Details: Undeployed Changes and Deploy Details: Existing Configuration pages to determine which configuration changes you must deploy, as well as which configuration changes have previously been deployed. The Services page indicates which services need to be restarted, if any, when configuration changes have occurred. 2. Server Status Portlet messages: Page 4 of 15
3.2.1 Server Status Portlet Messages To troubleshoot Server Status Portlet messages, refer to the Server Status Portlet Messages section. 3.2.1.1 Message: active Explanation: The server is currently active and UWCC is able to connect to it successfully without any problems. None 3.2.1.2 Message: Global User not configured. Explanation: The Server Status portlet uses the Global user ID and password configured in the Configuration Server Properties page. If the global user ID is blank, this message appears in the portlet. Typically, the Global user ID either has an associated credential user for each server defined in the Unicenter WCC instance or is a valid user ID on the back-end job management server. Go to the Environment tab and then to the Configuration Server Properties page. Define a Global user ID for the Server Status portlet authentication. This Global user ID mapped with a credential user ID will be used to verify the status of all the servers visible in the portlet. 3.2.1.3 Message: Credential User not configured. Explanation: A credential user has not been configured for this server. UWCC attempted to log in and connect to the server using the global user ID and password defined in the Configuration Server Properties page, but the login failed. One reason for a login failure is that the Global user ID and/or password do not match the back-end server user ID and/or password. Another reason for this message may be because the Global user ID doesn t have a corresponding credential user. A credential user matching the Global user ID must be configured for the back-end server. AutoSys: If the Cross-Platform Indicator has been set to true, the related CCI Link is also up. CA-7: The related CCI link is up. Go to the Security tab in the Configuration Manager and add a credential user for this server through the Credential Users page. Verify that the credential user ID matches the Global user ID for this server. Verify the Server Status using the Verify Server Status page. If any error messages or alerts appear when you re-verify the status, refer to the JCC Messages section for troubleshooting steps. 3.2.1.4 Message: Unable to login to server. Invalid Credential User. Explanation: A credential user has been configured for this server. But, either the user ID and/or password of the configured credential user are invalid. This resulted in a logon failure. You have entered an invalid user ID and/or password for the configured credential user and are unable to log in. AutoSys: If the Cross-Platform indicator has been set to true, the related CCI Link is also up. CA-7: The related CCI link is up. Go to the particular Credential user for this server and verify if its alias user ID and/or password are correct. Page 5 of 15
If your enterprise uses a common user ID and different passwords for multiple systems, and you are using the Server Password feature, check whether the server password defined in the credential user is correct. Check if the alias or the server password (whichever is applicable) was changed or has expired recently. If the password has changed, go to this credential user in the Configuration Manager on the Security tab and change the password. You can check the validity of the credential user in the Credential User Summary Status portlet. If any error messages or alerts appear when you re-verify the status, refer to the JCC Messages section for troubleshooting steps. CA-7: Review the server definition. 3.2.1.5 Message: Unable to access server. Explanation: The server is currently unavailable. UWCC is unable to connect to it. The server and/or network connection might be down. Try to ping the server using the command: ping <server_name or IP_address> If you are unable to ping the server using the server_name but are able to ping using the IP_address, then check the Domain Name Server (DNS) settings. Ask this question - has any configuration on the server changed recently? If yes, then change the corresponding configuration in the UWCC server configuration. To help diagnose the problem, visit the Verify Server Status page for this server. o On this page, when you enter the credentials and click Verify, a list of error(s), alert(s) and confirmation(s) appears. Refer to the JCC Messages section for troubleshooting steps. AutoSys r4.0 or r4.5: Verify the following Event Processor Host Name Event Processor Listener Port (RCS or Java Listener Port.): By default, the value of this port is 4444. Event Server Connection Port. Instance Name, User ID and/ or Password. Event Server Host Name, Event Server Connection Port, Event Server Database Name and Instance Database Type. If the Event Server Database type is Oracle, check the TNS Name. If the Cross-Platform indicator has been set to true, verify if the related CCI Link is up. Check the CCI Link status from the CCI Links Status page. If the CCI Link status is inactive, check if the CA-Unicenter (Remote) service is running on the UWCC server AutoSys r11.0: Verify the following Check whether the Application Server is running. The CA Unicenter AutoSys JM Application Server service should be running. If the service is not running, please start the service on the AutoSys server. The Application Server Host Name Instance name Monitor user ID and password Port number of application server Use the command netstat -an to see if the AutoSys server machine is listening on the Application Server Port Listener configured port number. Page 6 of 15
Verify that UWCC and the AutoSys r11.0 instances are using the same Dylan PMUX/SSL settings. Run the following command on both the UWCC and AutoSys machines to configure the Dylan PMUX/SSL settings: configedit port=<port> display configedit portrange=49152-50176 display CA-7: Verify the following The CCI Link status from the CCI Links Status page. o If the CCI Link status is inactive, check whether the CA-Unicenter (Remote) service is running on the UWCC server. If the service is not running, start/restart the service. o If the CCI Link status is active, check whether the CPS Manager and other mainframe server tasks are running on the mainframe server. Component Name. Monitor ID and Monitor Password. 4 Verifying Server Status On the Server Status page, you can verify the status of a UWCC server. When you enter the credentials and click Verify, a list of errors, alerts and confirmation messages appear. To troubleshoot the server status, first review the error messages, then review the warning messages and finally review the confirmation messages. 4.1 JCC Messages The following table summarizes the portlet error messages: Error Code Type Message JCC1000 Confirmation The CCI link is active. JCC1001 Confirmation The CPS Manager for CCI links is available. JCC1995 Error The CA-Unicenter (Remote) Service is not running. Please start or restart the CA-Unicenter Services in the Services panel. JCC1996 Error The CCI link is not defined. Please check the CCI definitions in ccirmtd.rc. JCC1997 Error The CPS Manager is unavailable. Please start or restart the CA-Unicenter Services in the Services panel. JCC1998 Error The CCI link is inactive. Please check the CA-Unicenter Services, ccirmtd.rc and/or the network connection. JCC1999 Error The CCI link is down. Please check the CA-Unicenter Services, ccirmtd.rc and/or the network connection. JCC2000 Alert The user credentials matched successfully. JCC2999 Alert No matching user credentials were found. JCC3000 Confirmation The server status is active. JCC3988 Error Server verification failed due to improper server/user details. Page 7 of 15
JCC3989 Error Error occurred while trying to verify the CCI Link associated with the selected server. JCC3990 Error Error occurred while trying to initialize connection to the CA-7 server. JCC3991 Error Error occurred while trying to initialize connection to the AutoSys server. JCC3992 Error Error occurred while retrieving CCI Link definition for the selected server. JCC3993 Error Error occurred while retrieving server definition. Please check the server profile configuration. JCC3994 Error Error occurred while fetching credentials for user. Please check the server profile configuration. JCC3995 Error The server is not defined. Please check the server profile configuration. JCC3996 Error A configuration exception occurred during processing. JCC3997 Error An authorization exception occurred during processing. JCC3998 Error The server status is unknown. The server and/or network connection may be down. JCC3999 Error The server status is down. The server and/or network connection may be down. 4.1.1 CCI Link Messages 4.1.1.1 Message: JCC1000: The CCI link is active. Explanation: The CCI Link is currently active. There are no connection problems for this link. None. 4.1.1.2 Message: JCC1001: The CPS Manager for CCI links is available. Explanation: The CPS Manager process is running on the CA-7 server. None. 4.1.1.3 Message: JCC1995: The CA-Unicenter (Remote) Service is not running. Please start or restart the CA-Unicenter Services in the Services panel Explanation: The indicated service is not running on the UWCC server. Start/ Restart CA-Unicenter (Remote) Service through Configuration Manager s Services tab or the Windows Services panel. 4.1.1.4 Message: JCC1996: The CCI link is not defined. Please check the CCI definitions in ccirmtd.rc. Explanation: This message may appear when a user is trying to verify a CCI link that another user has deleted. Visit the CCI links list page. Click the Refresh List button. Check whether the CCI link exists in the CCI links list page. If the CCI link does not appear in the list, recreate the link and check the CCI link status through the CCI Link Status page or portlet. Verify the details of the CCI link you are trying to verify in the ccirmtd.rc file. Multiple ccirmtd.rc files may exist on a server, however, only one of these ccirmtd.rc files will be in use. Page 8 of 15
o o To locate the ccirmtd.rc file that is in use, run the cci_config_locator utility from a command prompt on the UWCC server. Open the ccirmtd.rc file and verify whether the details for the CCI link you are trying to verify are contained in this file. If there is no entry for the specific CCI link in this file, try creating the link again through UWCC. Deploy and then restart the CA-Unicenter (Remote) service. Note: When working with the Deploy tab, you can use the Deploy Details: Undeployed Changes and Deploy Details: Existing Configuration pages, to determine which configuration changes you need to deploy, as well as which configuration changes have already been deployed. The Services page indicates which services need to be restarted, if any, when configuration changes have occurred. Open the configfileman.properties file available in the <UWCC_Install_directory>\Unicenter Workload Control Center\ConfigServer\webapps\UEJMConfiguration\WEB- INF\classes\com\ca\uejm\resources directory. Verify that the value of the CA- 7_CONFIG_PATH is the same as the output of the cci_config_locator utility. 4.1.1.5 Message: JCC1997: The CPS Manager is unavailable. Please start or restart the CA-Unicenter Services in the Services panel. Explanation: The CPS Manager process might not be running on the CA-7 server. Start/ Restart CA-Unicenter (Remote) Service through Configuration Manager s Services tab or the Services panel. Check whether the CPS Manager task is started on the mainframe. If the task is not started, start it on the mainframe. 4.1.1.6 Message: JCC1998: The CCI link is inactive. Please check the CA-Unicenter Services, ccirmtd.rc and/or the network connection. Explanation: There is no CCI connection for the specified CCI link. Check the CA-Unicenter (Remote) service. Start / Restart this service through Configuration Manager s Services tab or the Services panel. Also make sure the IP name and Port Number fields are correctly configured for the CCI Link. Changing any CCI Link properties requires a deploy and then a restart of CA- Unicenter (Remote) Service. Note: When working with the Deploy tab, you can use the Deploy Details: Undeployed Changes and Deploy Details: Existing Configuration pages, to determine which configuration changes you need to deploy, as well as which configuration changes have already been deployed. The Services page indicates which services need to be restarted, if any, when configuration changes have occurred. The CA-7 server and/or network connection might be down. Try to ping the server using the command: ping <server_name or IP_address> If you are unable to ping the server using the server_name but are able to ping using the IP_address, then check the Domain Name Server (DNS) settings. For the CCI connection to work properly, you must have a unique CCI node name on both the local and remote machines. This CCI node name can either be the machine name, or an 8-character alias. CCI only evaluates the first eight characters of the machine name. If you work primarily on distributed systems, ensure that you have a unique CCI node name (either with the machine name or the alias) for the UWCC server as well as any AutoSys servers for which you have defined a CCI connection. Page 9 of 15
Verify the details of the CCI link you are trying to verify in the ccirmtd.rc file. Multiple ccirmtd.rc files may exist on a server, however, only one of these ccirmtd.rc files will be in use. To locate the ccirmtd.rc file that is in use, run the cci_config_locator from the command prompt on the UWCC server. Open the ccirmtd.rc file and verify whether the details for the CCI link you are trying to verify are present in this file. If there is no entry for the specific CCI link in this file, try creating the link again through UWCC. Restart the CA-Unicenter (Remote) service. If you see an entry for the specific CCI link, then check the log file - ccilog_<most_recent_timestamp>.txt (e.g. ccilog_ 7102006.txt) located in the C:\Program Files\CA\SharedComponents\cci\DATA directory to help diagnose the problem. You can turn tracing on and generate the CPS log to help diagnose the CCI/ CPS connectivity problems. To turn tracing/ debug on, set the environment variables CPS_LOG=<DirPath> (e.g. C:\temp) and CPS_TRACE=1 and restart the UWCC server. Make sure that the directory specified by <DirPath> exists on the server. Turning tracing/debug on will create a debug log at the CPS_LOG location. Note: When AutoSys with the Cross-Platform Indicator is set to True and the JCC1998 message The CCI link is inactive appears in the Verify Server page, you can still connect to the AutoSys server in the Job Editor, Job Flow Monitoring and Job Status Console. You can also view job status and job definitions. However, you will not correctly see the cross-platform linkages. 4.1.1.7 Message: JCC1999: The CCI link is down. Please check the CA-Unicenter Services, ccirmtd.rc and/or the network connection. Explanation: There is no CCI connection for the specified CCI link. Refer to the Recommended Action section for the JCC1998 message. 4.1.2 Server Verification Messages 4.1.2.1 Message: JCC2000: The user credentials matched successfully. Explanation: The configured credential user was found for this server in the UWCC configuration. None. 4.1.2.2 Message: JCC2999: No matching user credentials were found. Explanation: No configured credential user was found for this server in the UWCC configuration, or the available credentials do not match any credential found for the back-end server. If the portal user ID is the same as the user ID for the back-end server and system, UWCC uses the portal user ID and password to access the back-end server or system. For a successful authentication, the Portal user ID and password must match the backend server user ID and password. Also, verify that the user password has not changed or expired. If the previous bullet did not apply, you might need to define a credential user for this server,. You will need to create a Credential user ID with an Alias matching a granted AutoSys or CA-7 user ID, for example Credential user ID: ejmcommander Alias = <CA-7_USER> or <AUTOSYS_USER> After creating a Credential user, verify the server again. If adding a credential user doesn t resolve the problem, review the other messages that appeared on the Server Verification page. Page 10 of 15
If there is an existing Credential user for this server, the credentials may have been entered incorrectly. Re-enter and re-save the credentials. The Credential user ID for this server might have expired on the UWCC server; therefore, you must verify that the Credential user ID is active on the UWCC server. Verify the Enable Credential Expiration and Days Credential is Active details of this Credential user. If there is a related Credential Group, verify whether the Credential Group user ID and password are correct. Also check whether the related Credential Group has expired. Verify the Enable Credential Expiration and Days Credential is Active details of the related Credential group. 4.1.2.3 Message: JCC3000: The server status is active. Explanation: A connection to the server could be established through UWCC. None. 4.1.2.4 Message: JCC3995: The server is not defined. Please check the server profile configuration. Explanation: This message may appear when a user is trying to verify the server and another user has deleted the server. Visit the Servers list page. Click the Refresh List button. Check whether the server exists in the Servers list page. 4.1.2.5 Message: JCC3996: A configuration exception occurred during processing. Explanation: An internal exception occurred during the processing of this request. All data related to the configuration is stored in a profiles.xml file located in the <UWCC_Install_directory>\Unicenter Workload Control Center\ConfigServer\config\working directory. This exception suggests that the profiles.xml file is either missing or corrupt. Check whether the profiles.xml file exists in the <UWCC_Install_directory>\Unicenter Workload Control Center\ConfigServer\config\working directory. If the files exists, it might be corrupt. Please contact CA Technical Support. 4.1.2.6 Message: JCC3997: An authorization exception occurred during processing. Explanation: UWCC uses the portal user ID and password or the configured Credential user details for connecting to the server. This exception is appears when the user ID and/ or password for the back-end server are invalid. If the portal user ID is the same as the user ID for the back-end server and system, UWCC uses the portal user ID and password to access the back-end server or system. For successful authentication, the Portal user ID and password must match the back-end server user ID and password. Also, verify that the user password has not changed or expired. The user ID and password supplied on this page must match the back-end server s user ID and password. The user ID and password are case sensitive. Please check whether you entered the user ID and/ or password in the proper case or if Caps lock is on. AutoSys 4.x: Verify that there is a valid IP address for the UWCC server in the validips file for RCS or the Java Listener. If the IP address is an issue, you will see an error in the asrcslsn.log/jil.log. Page 11 of 15
4.1.2.7 Message: JCC3998: The server status is unknown. The server and/or network connection may be down. Explanation: The connection to the server failed due to unknown reasons. The server or network connection might not be available. Refer to the Recommended Action section for the JCC3999 message. 4.1.2.8 Message: JCC3999: The server status is down. The server and/or network connection may be down. Explanation: An exception occurred while trying to connect to the server. This exception might be due to the server or network being down. Check whether the server is up. If the server is not up, start it. Also, try to ping the server using the following command: ping <server_name or IP_address> If you are unable to ping the server using the server_name but are able to ping using the IP_address, then check the Domain Name Server (DNS) settings. AutoSys 4.0 or 4.5 Server: Verify the following: Event Processor host name Event Server host name, Event Server Database Name and Instance Database type. Check the Configuration log file located in the <UWCC_Install_directory>\ Logs\application\config\uejm_configuration_servlet.log. If there is a Command Agent Failed. or Failed connecting to Primary event server error at the bottom of the Configuration log file, then check your Event Server configuration (ports, names, etc.). If the Event Server database type is Oracle, make sure the same SID was used for Event Server Database Name and TNS Names fields. If the Event Server is SQLServer 2000 (a version prior to SQLServer Service Pack 4), the netstat command output on the SQL server machine may show the database port (usually,1433) as listening, but an SQLServer 2000 feature does not allow connections to SQL Server from remote clients. The Windows Event Viewer on the SQL Server machine will display the error remote clients not allowed to connect due to security concerns. The resolution of this problem is to apply SQL Server SP4. The SQLServer Client/Server Network Utility may help to identify the port number which the clients use to connect to SQLServer. Event Processor listener port (RCS/Java Listener): By default the value of this port is 4444. Verify that the RCS/JavaListener is configured properly using the steps below: o Use the command netstat -an to see whether the machine is listening on the o UWCC Event Processor Listener configured port number. Ping from the UWCC server machine to the AutoSys machines RCS/Java Listener port to verify connectivity. Verify valid ips for the Listener (RCS/Java Listener). You will find an error in the asrcslsn.log/jil.log if the ips are an issue. AutoSys r11.0 Server: Verify the following: Check whether the Application Server is running. The CA Unicenter AutoSys JM Application Server service should be running. If it is not running, start this service on the AutoSys server. The Application Server Host Name Instance name Monitor user ID and password Port number of the application server Page 12 of 15
Use the command netstat -an to see whether the AutoSys server machine is listening on the Application Server Port Listener configured port number. PMUX/SSL settings CA-7 Server: Verify the following: The CCI Link status from the CCI Links Status page. o If the CCI Link status is inactive, check whether the CA-Unicenter (Remote) service is running on the UWCC server. If it is not running, start/restart this service. o If the CCI Link status is active, check whether the CPS Manager and other mainframe server tasks are running on the mainframe server. Component Name. Monitor ID and Monitor Password. 4.1.2.9 Message: JCC3988: Server verification failed due to improper server/user details. Explanation:. This message appears when an internal exception is thrown by the verification API. The message indicates that either the server name, user ID and/or password are missing as inputs to the verification API. Verify whether a valid user ID and password are supplied in the server configuration. 4.1.2.10 Message: JCC3989: Error occurred while trying to verify the CCI Link associated with the selected server. Explanation:.For a CA-7 server or an AutoSys server with Cross-Platform Indicator set to true, before trying to connect to the server, UWCC checks whether the related CCI link is active. This message indicates that there was an exception thrown by the API while running the rmtcntrl or ccii command for the related CCI link. Check the status of the CCI link from the CCI Links Status page. Try running the rmtcntrl command on the UWCC server from a command prompt by using the following command: rmtcntrl <CCI_link_name> Try running the ccii command on the UWCC server from a command prompt by using the following command: ccii <CCI_link_name> 4.1.2.11 Message: JCC3990: Error occurred while trying to initialize connection to the CA7 server. Explanation: This message is an internal exception that is raised when there is an unknown and unexpected error in initializing the connection to the CA-7 server. Contact your System Administrator to report the problem. 4.1.2.12 Message: JCC3991: Error occurred while trying to initialize connection to the AutoSys server. Explanation: This message is an internal exception that is raised when there is an unknown and unexpected error in initializing the connection to the AutoSys server. Contact your System Administrator to report the problem. 4.1.2.13 Message: JCC3992: Error occurred while retrieving CCI Link definition for the selected server. Page 13 of 15
Message: JCC3993: Error occurred while retrieving server definition. Please check the server profile configuration. Message: JCC3994: Error occurred while fetching credentials for user. Please check the server profile configuration. Explanation: All data related to the server profile configuration is stored in the profiles.xml file located in the <UWCC_Install_directory>\Unicenter Workload Control Center\ConfigServer\config\working directory. This exception suggests a problem with the profiles.xml file. This file is either missing or corrupt. Check whether the profiles.xml file exists at the <UWCC_Install_directory>\Unicenter Workload Control Center \ConfigServer\config\working directory. If the profiles.xml file exists, then it may be corrupt. Please contact your System Administrator to report the problem. 5 Frequently Asked Questions 1. What log files can I refer to? You can refer to the uejm_configuration_servlet.log file, which is present in the <UWCC_Install_root>\Logs\application\config directory. 2. How do I switch the debug mode to ON to generate debug messages in the log file? Open the log4j.properties file located in the <UWCC_Install_root>\Unicenter Workload Control Center \Logs\application\config directory.stop the the CA- Unicenter Workload Control Center Configuration server service. In the log4j.properties file, replace the INFO and ERROR strings with DEBUG. Save and close the file. Start/Restart the CA-Unicenter Workload Control Center Configuration server service. The debug log messages will now be generated in the uejm_configuration_servlet.log file (Refer to answer to Question1). 3. What are the minimum requirements for a CA-7 Mainframe server to work with UWCC r1 SP4? The following requirements must be met or exceeded for your z/os server only: Unicenter CA-7 Job Management (Unicenter CA-7) 3.3, FMIDs CL233S0 and CL233C0 at SP6 OR Unicenter CA-7 Job Management (Unicenter CA-7) r11, FMID CL2B000 at SP0 or higher CA-CPS (CA-Common Product Services) 1.0, FMID CWR1000 at SP0 with APAR QO75563 OR CA-CPS (CA-Common Product Services) 1.0 at SP1 or higher TCP/IP (IBM or Unicenter TCPaccess Communications Server) CA Common Services for z/os and OS/390 SP5 or higher, including the following: - CAIRIM (CA Resource Initialization Manager), FMID CS91000 - CAICCI, FMID CW41100 or CW42100 - CA-ViewPoint, FMID CAG3000 - CAIENF (CA Event Notification Facility), FMID CW11000 or CW21000 Page 14 of 15
- CA-C Language Runtime Facility, FMID CF33100 4. When I try to connect to the CA-7 server, that has an active status, using Job Flow Monitoring, I receive the following error: What should I do to resolve this problem? The common status monitoring function of Job Flow Monitoring uses the user ID and password that is defined in the CA-7 Server configuration definition- not the user ID that is currently signed on to the portal. In the Configuration function, choose the Setup tab and select the Servers menu item. Choose the CA-7 server you ve defined here and ensure that the Monitor ID and Monitor Password fields are correctly set to a valid user ID. 5. What are the considerations while naming a CCI node? For the CCI connection to work properly, you must have a unique CCI node name on both the local and remote machine. This CCI node name can be either the machine name and/or an 8-character alias. CCI only evaluates the first eight characters of the machine name. If you work primarily on distributed systems, ensure that you have a unique CCI node name, either with the machine name or the alias, for the UWCC server as well as any AutoSys servers for which you have defined a CCI connection. 6. How can I turn tracing on for the CA-7 server to help in debugging CCI/CPS connectivity problems? You can turn tracing on and generate the CPS log to help diagnose the CCI/ CPS connectivity problems. To turn tracing/debug on, set the environment variables CPS_LOG=<DirPath> (e.g. C:\temp) and CPS_TRACE=1, and restart the server. Make sure that the directory specified by <DirPath> exists on the server. Completing these steps will create a debug log at the CPS_LOG location. Page 15 of 15