Messages GI0700 through GI0799
This topic contains messages for the BMC Impact Integration for z/OS product.
Number | Description | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
GI0702I | GIyTxxxx FROM: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX Explanation: An Impact Manager has accepted a connect request from the client task identified by GICTxxxx or an Impact Manager has connected/disconnected to/from the Integration Server task identified by GISTxxxx. This message identifies the remote host and port number of the connection. Processing continues. This message follows messages GI0684I and GI0712I. User response: None. This message is informational. | ||||||||||
GI0712I | GICTxxxx RECEIVED CONNECTION STATUS - status Explanation: The client connection task identified by GICTxxxx has received a notification that the status of the connection to an Impact Manager has changed. Status can be DOWN, OPEN, PEND, SYNCH, or FAIL. Processing continues. This message is followed by message GI0702I. User response: None. This message is informational. | ||||||||||
GI0716E | GICTxxxx error-text-from-received-reply-error Explanation: An Impact Manager has replied to a message sent to it by the client connection task identified by GICTxxxx and the message had an error in it. This message shows the error text from the error reply. Processing continues. This message follows message GI0718E. User response: Contact BMC Support. | ||||||||||
GI0718E | GICTxxxx ERROR REPLY RECEIVED FOR MSGHANDLE hhhhhhhh ERROR CODE eeee Explanation: An Impact Manager has replied to a message sent to it by the client connection task identified by GICTxxxx and the message had an error in it. This message identifies the task-id which received the error reply by GICTxxxx, the message handle of the message in error by hhhhhhhh, and the error code in the reply by eeee. Processing continues. This message is followed by message GI0716E. User response: Contact BMC Support. | ||||||||||
GI0719E | GIyTxxxx RETURN CODE eeeee FROM CALL TO iiiiiiiiiiiiiiii Explanation: A request for a BMC Impact Integration Developer Kit API service has failed in the task identified by GIyTxxxx where y is C for a client task, s is for the Integration Server task, and xxxx is the task number. The return code from the service is eeeee and iiiiiiiiiiiiiiii identifies the requested service. Processing continues. This message is followed by message GI0720E. User response: Contact BMC Support. | ||||||||||
GI0720E | GIyTxxxx error-text-from-failed-IIDK-API-service-request Explanation: A request for a BMC Impact Integration Developer Kit API service has failed in the task identified by GIyTxxxx where y is C for a client task, s is for the Integration Server task, and xxxx is the task number. The error text explaining the reason for the failure is shown by this message. Processing continues. This message follows message GI0719E. More than one of these messages may be issued to display all of the error text for the failure. User response: Contact BMC Support or try to correct the error using information contained in this message. | ||||||||||
GI0747E | GIyTxxxx CONNECTION TERMINATING - UNABLE TO SEND MESSAGE Explanation: The application message was not sent because the connection to the Impact Manager is terminating. The task managing the connection is identified by GIyTxxxx where y is C for Client or S for Server; xxxx is the task number. Processing continues. The message will not be sent. User response: Instruct the sending application to resend the application message. | ||||||||||
GI0748E | GIyTxxxx MESSAGE EXPIRED - NOT SENT Explanation: The application message was not sent before the expiration period had passed. The expiration period is determined by the sending application. The task managing the connection is identified by GIyTxxxx where y is C for Client or S for Server; xxxx is the task number. Processing continues. The sending application will be posted if necessary. The message will not be sent. User response: Instruct the sending application to resend the application message. | ||||||||||
GI0749E | GIyTxxxx PROCESS QUEUE LIMIT EXCEEDED. TERMINATING CONNECTION. Explanation: The maximum number of messages have been queued to the connection to be sent. The task managing the connection is identified by GIyTxxxx where y is C for Client or S for Server; xxxx is the task number. The GME connection is terminated. User response: The GME connection can be restarted with BBI command: .E PARM,AAOGMExx,RESYNC However, before attempting the RESYNC you should check to see if the condition that caused the error still exists. The number of ALERTs that must be re-synced may result in an immediate termination of the connection upon a RESYNC. In this case the number of ALERTS will have to be reduced before a successful RESYNC will occur. | ||||||||||
GI0753E | GIyTxxxx RETURN CODE eeeee FROM CALL TO iiiiiiiiiiiiiiii Explanation: A request for a BMC Impact Integration Developer Kit API service has failed in the task identified by GIyTxxxx where y is C for a client task, s is for the Integration Server task, and xxxx is the task number. The return code from the service is eeeee and iiiiiiiiiiiiiiii identifies the requested service. Processing continues. This message is followed by message GI0754E. User response: Contact BMC Support. | ||||||||||
GI0753E | GIyTxxxx RETURN CODE eeeee FROM CALL TO iiiiiiiiiiiiiiii Explanation: A request for a BMC Impact Integration Developer Kit API service has failed in the task identified by GIyTxxxx where y is C for a client task, s is for the Integration Server task, and xxxx is the task number. The return code from the service is eeeee and iiiiiiiiiiiiiiii identifies the requested service. Processing continues. This message is followed by message GI0764E. User response: Contact BMC Support. | ||||||||||
GI0754E | GIyTxxxx error-text-from-failed-IIDK-API-service-request Explanation: A request for a BMC Impact Integration Developer Kit API service has failed in the task identified by GIyTxxxx where y is C for a client task, s is for the Integration Server task, and xxxx is the task number. The error text explaining the reason for the failure is shown by this message. Processing continues. This message follows message GI0753E. More than one of these messages may be issued to display all of the error text for the failure. User response: Contact BMC Support or try to correct the error using information contained in this message. | ||||||||||
GI0760E | GIyTxxxx INVALID GFH ID Explanation: An improperly formatted message has been passed to the transform routine in the task identified by GIyTxxxx where y is C for a client task, s is for the Integration Server task, and xxxx is the task number. The task is terminated. User response: Contact BMC Support. | ||||||||||
GI0761E | GIyTxxxx INVALID GFH VERSION Explanation: An improperly formatted message has been passed to the transform routine in the task identified by GIyTxxxx where y is C for a client task, s is for the Integration Server task, and xxxx is the task number. The task is terminated. User response: Contact BMC Support. | ||||||||||
GI0762E | GIyTxxxx INVALID GDA ID Explanation: An improperly formatted message has been passed to the transform routine in the task identified by GIyTxxxx where y is C for a client task, s is for the Integration Server task, and xxxx is the task number. The task is terminated. User response: Contact BMC Support. | ||||||||||
GI0764E | GIyTxxxx error-text-from-failed-IIDK-API-service-request Explanation: A request for a BMC Impact Integration Developer Kit API service has failed in the task identified by GIyTxxxx where y is C for a client task, s is for the Integration Server task, and xxxx is the task number. The error text explaining the reason for the failure is shown by this message. Processing continues. This message follows message GI0763E. More than one of these messages may be issued to display all of the error text for the failure. User response: Contact BMC Support or try to correct the error using information contained in this message. | ||||||||||
GI0765E | GIyTxxxx REQUIRED DATA MISSING/INVALID, EVENT NOT SENT Explanation: An improperly formatted message has been passed to the transform routine in the task identified by GIyTxxxx where y is C for a client task or S for the Integration Server task and xxxx is the task number. The task will continue, but the event will not be sent to the BIM cell. User response: If using 'IMFEXEC WARN', change to 'IMFEXEC Alert'. Otherwise, contact BMC Support. | ||||||||||
GI0770E | GIyTxxxx USER uuuuuuuu NOT AUTHORIZED Explanation: The user on a BMC EM/SIM console tried to schedule an EXEC for execution in a BMC AMI Ops Automation PAS. The attempt was rejected because the user was not authorized. Where:
Exec indicated in message GI0792E is not executed. User response: Contact your security administrator and request that the user ID in message GI0792E is given READ access to EXECs. | ||||||||||
GI0771E | GIyTxxxx If unable to resolve the problem then contact your Explanation: This message only appears in the BMC EM/SIM console and instructs the user who should be contacted for the error messages that preceded this message. Variable values in GIyTxxxx are:
User response: If you were unable to correct the problem from the previous message, then you should contact one of these persons to resolve this issue. | ||||||||||
GI0772E | GIyTxxxx RACF FAILURE SAF RC=aa..aa, RACF RC=bb..bb, RACF REAS=cc..cc Explanation: The user on a BMC EM/SIM console tried to schedule an EXEC for execution in a BMC AMI Ops Automation PAS. The attempt failed because RACROUTE REQUEST=VERIFY returned a non-zero return code. Where:
The Exec indicated in message GI0792E is not scheduled for execution. User response: Contact your security administrator for a resolution. Reference the IBM z/OS Security Server RACROUTE Macro Reference for more information regarding the meaning of return codes. | ||||||||||
GI0773E | GIyTxxxx EXEC MANAGER QUEUE IS NOT ALIVE Explanation: The user on a BMC EM/SIM console tried to schedule an EXEC for execution in a BMC AMI Ops Automation PAS, but the EXEC Manager is currently not running. Where:
The EXEC indicated in message GI0792E is not scheduled for execution. User response: Obtain a console dump of the BMC AMI Ops Automation PAS with options SDATA=(CSA, RGN, TRT, GRSQ) in case it may be needed by BMC support for analysis. Restart your BMC AMI Ops Automation PAS and retry the scheduling of the EXEC. Review your logrec and the BMC AMI Ops Automation job log and journal for any abends that may have occurred. Look on eFix for resolutions to the abend. | ||||||||||
GI0774E | GIyTxxxx ESD POINTER ZERO IN SMD Explanation: The user on a BMC EM/SIM console tried to schedule an EXEC for execution in a BMC AMI Ops Automation PAS, but the EXEC Manager is currently not running. Where:
The EXEC indicated in message GI0792E is not scheduled for execution. User response: Obtain a console dump of the BMC AMI Ops Automation PAS with options SDATA=(CSA, RGN, TRT, GRSQ) in case it may be needed by BMC support for analysis. Restart your BMC AMI Ops Automation PAS and retry the exec. Review your logrec and the BMC AMI Ops Automation job log and journal for any abends that may have occurred. Look on eFix for resolutions to the abend. | ||||||||||
GI0775E | GIyTxxxx EXEC MANAGER INACTIVE Explanation: The user on a BMC EM/SIM console tried to schedule an EXEC for execution in a BMC AMI Ops Automation PAS, but the EXEC Manager is currently not running. Where:
The EXEC indicated in message GI0792E is not scheduled for execution. User response: Obtain a console dump of the BMC AMI Ops Automation PAS with options SDATA=(CSA, RGN, TRT, GRSQ) in case it may be needed by BMC support for analysis. Restart your BMC AMI Ops Automation PAS and retry the exec. Review your logrec and the BMC AMI Ops Automation job log and journal for any abends that may have occurred. Look on eFix for resolutions to the abend. | ||||||||||
GI0776E | GIyTxxxx EXEC NOT FOUND: aaaaaaaa Explanation: The user on a BMC EM/SIM console tried to schedule an EXEC for execution in a BMC AMI Ops Automation PAS. The attempt failed because the EXEC name specified does not exist in the EXEC library. Where:
Incoming request is ignored. User response: Verify the EXEC name to ensure the correct name was used. If it is correct; make the EXEC available to the BMC AMI Ops Automation PAS by including it in one of the libraries identified in the SYSPROC DD statement in the PAS JCL. | ||||||||||
GI0777E | GIyTxxxx EXEC aaaaaaaa IS DISABLED Explanation: The user on a BMC EM/SIM console tried to schedule an EXEC for execution. The attempt failed because the EXEC name specified is marked DISABLED in the BMC AMI Ops Automation EXEC Manager. Where:
EXEC is not scheduled for execution. User response: Enable the EXEC and try again. | ||||||||||
GI0778E | GIyTxxxx LAUNCHING EXECS NOT ALLOWED FROM iiii Explanation: The user on a BMC EM/SIM console tried to schedule an EXEC for execution in a BMC AMI Ops Automation PAS. The attempt failed because EXEC=NO was specified in the AAOGMExx member for this Impact Manager. Where:
The EXEC indicated in message GI0792E is not scheduled for execution. User response: To enable the ability for BMC Impact Explorer users to schedule EXECs for execution, specify "EXEC=Y" in the AAOGMExx member. | ||||||||||
GI0779I | GIyTxxxx EXEC: aa...aa SCHEDULED IN MAINVIEW AUTOOPERATOR Explanation: The user on a BMC EM/SIM console or an exec running on the cell requested the BMC AMI Ops Automation EXEC to be scheduled. Where:
EXEC request is queued to run. User response: Informational message | ||||||||||
GI0780W | GIyTxxxx SLOT NOT FOUND: aa...aa Explanation: While parsing an incoming BMC IM BAROC event an expected slot name was not found in the event. This message is issued by the task identified by GIyTxxxx. Where:
Incoming event is ignored. User response: Contact BMC Support. | ||||||||||
GI0781W | GIyTxxxx status SLOT CONTAINS UNEXPECT VALUE: aa...aa Explanation: While parsing an incoming BMC IM BAROC event. The status slot did not contain one of the following values: OPEN, ACK, RESPONSE, or CLOSED. This message is issued by the task identified by GIyTxxxx. Where:
Incoming event is ignored. User response: Contact BMC Support. | ||||||||||
GI0782E | GIyTxxxx RETURN CODE aaaaa FROM CALL TO bbbbbbbb Explanation: While parsing an incoming BMC IM BAROC event. An unexpected return code was returned from the specified internal function. This message is issued by the task identified by GIyTxxxx. Where:
Incoming event is ignored. User response: Contact BMC Support. | ||||||||||
GI0783E | GIyTxxxx RETURN CODE aaaaa FROM CALL TObb...bb Explanation: While parsing an incoming BMC IM BAROC event. An unexpected return code was returned from the specified BMC IIM API. This message is issued by the task identified by GIyTxxxx. Where:
Incoming event is ignored. User response: Contact BMC Support. | ||||||||||
GI0784E | GIyTxxxx aaaaaaaaaaaaaa............aaaaaaaaaaaaaaa Explanation: While parsing an incoming BMC IM BAROC event. An unexpected return code was returned from the specified BMC IIM API. This message contains the text describing the return code. This message is issued by the task identified by GIyTxxxx. Where:
Incoming event is ignored. User response: Contact BMC Support. | ||||||||||
GI0785W | GIyTxxxx ERROR EXTRACTING FIELD FROM mc_ueid IN MOD EVENT: aa...aa Explanation: While parsing an incoming BMC IM BAROC mod event the mc_ueid slot value was not in the expected format. This message is issued by the task identified by GIyTxxxx. Where:
Incoming event is ignored. User response: Contact BMC Support. | ||||||||||
GI0786I | GIyTxxxx UNEXPECTED NEW EVENT RECEIVED CLASS: aa...aa Explanation: While parsing an incoming BMC IM BAROC event the incoming event belongs to an unexpected/unknown event class. This message is issued by the task identified by GIyTxxxx. Where:
Incoming event is ignored. User response: Contact BMC Support. | ||||||||||
GI0786I | GIyTxxxx UNEXPECTED MOD EVENT RECEIVED mc_ueid=aa...aa Explanation: While parsing an incoming BMC IM BAROC event the incoming mod event contains a mc_ueid that does not begin with BBO_ALRT_. This message is issued by the task identified by GIyTxxxx. Where:
Incoming event is ignored. User response: Contact BMC Support. | ||||||||||
GI0790E | GIyTxxxx RETURN CODE aaaaa FROM CSATOP ROUTINE Explanation: The user on a BMC EM/SIM console tried to delete an AO alert. The attempt was rejected because of an internal error in CSATOP function. This message is issued by the task identified by GIyTxxxx. Where:
Incoming request is ignored. User response: Contact BMC Support. | ||||||||||
GI0791D | GIyTxxxx DELETE ALERT - TOKEN= aa...aa, SSID=bb...bb, USER=cc...cc Explanation: The user on a BMC EM/SIM console tried to delete an AO alert. This message displays the token, ssid, and the user used to delete the alert. This message is issued by the task identified by GIyTxxxx. Where:
Incoming delete request is processed. User response: This message is displayed when debugging is turned on. | ||||||||||
GI0792E | GIyTxxxx EXEC exec NOT SCHEDULED. USERID userid FROM bim-node Explanation: This message informs you that the exec requested by a user from BIM was not executed because of an error as indicated in a previous message. Where:
Exec indicated in message is not executed. User response: Review previous messages for the problem that caused the exec not to be executed. | ||||||||||
GI0793E | GIyTxxxx INVALID USERID SPECIFIED Explanation: The USERID that the BMC EM/SIM console user specified in the REMOTE ACTION - SETUP z/OS USERID was either entered incorrectly or was not a userid valid on this system Where:
Exec indicated in message GI0792E is not executed. User response: Specify the user ID correctly and retry. If problem persists, contact your security administrator. | ||||||||||
GI0794E | GIyTxxxx INVALID PASSWORD Explanation: The password that the BMC EM/SIM console user specified in the REMOTE ACTION - SETUP z/OS USERID was either entered incorrectly or was not the correct password for the userid as shown in message GI0792E. Where:
Exec indicated in message GI0792E is not executed. User response: Specify the password correctly and retry. If problem persists, contact your security administrator. | ||||||||||
GI0795E | GIyTxxxx PASSWORD EXPIRED - CHANGE PASSWORD REQUIRED Explanation: The password that the BMC EM/SIM console user specified in the REMOTE ACTION - SETUP z/OS USERID has expired and must be changed before the userid can be used. Where:
Exec indicated in message GI0792E is not executed. User response: Change the password for the user. If problem persists, contact your security administrator. | ||||||||||
GI0796E | GIyTxxxx INVALID NEW PASSWORD SPECIFIED Explanation: The new password that the BMC EM/SIM console user specified in the REMOTE ACTION - SETUP z/OS USERID is invalid. Where:
Exec indicated in message GI0792E is not executed. User response: Specify a password that is valid. You will need to follow password rules for your system. If problem persists, contact your security administrator. | ||||||||||
GI0797E | GIyTxxxx USER NOT IN GROUP Explanation: The user ID that the BMC EM/SIM console user specified in the REMOTE ACTION - SETUP z/OS USERID has an invalid group definition. Where:
Exec indicated in message GI0792E is not executed. User response: Contact your security administrator. They need to correct the user ID as indicated in message GI0792E. | ||||||||||
GI0798E | GIyTxxxx FAILED DURING SECURITY INSTALLATION EXIT Explanation: The user ID that the BMC EM/SIM console user specified in the REMOTE ACTION - SETUP z/OS USERID did not pass your security exit validation. See message GI0792E for the problem user ID. Where:
Exec indicated in message GI0792E is not executed. User response: Contact your security administrator. | ||||||||||
GI0799E | GIyTxxxx USERID IS REVOKED Explanation: The user ID that the BMC EM/SIM console user specified in the REMOTE ACTION - SETUP z/OS USERID is revoked and cannot be used. See message GI0792E for the user ID that is revoked. Where:
Exec indicated in message GI0792E is not executed. User response: Contact your security administrator. |