Use the IXGCONN macro to connect a program to a specific log stream or disconnect a program from a specific log stream.
IXGCONN returns a unique connection identifier called a stream token on completion of the IXGCONN REQUEST=CONNECT request. Subsequent logger services use the stream token to identify the connection. If multiple applications connect to the same log stream, the log blocks written from the different applications are merged.
Note that a DASD-only log stream is single-system in scope. This means that only one system may connect to a DASD-only log stream, although there can be multiple connections from that one system.
For information about using the system logger services and the IXGCONN request, see z/OS MVS Programming: Assembler Services Guide which includes information about related macros IXGBRWSE, IXGDELET, IXGWRITE, IXGINVNT, and IXGQUERY.
The requirements for the caller are:
Environmental factor | Requirement |
---|---|
Minimum authorization: | Problem state with any PSW key. |
Dispatchable unit mode: | Task |
Cross memory mode: | PASN=HASN, any SASN |
AMODE: | 31-bit or 64-bit |
ASC mode: | Primary or access register (AR) |
Interrupt status: | Enabled for I/O and external interrupts. |
Locks: | No locks may be held. |
Control parameters: | None. |
If this condition occurs and there remains an expected use of a log stream, then a new log stream connection will be required.
If SAF is not available or if CLASS(LOGSTRM) is not defined to SAF, no security checking is performed. In that case, the caller is connected to the log stream with the requested or default AUTH parameter value.
Before issuing the IXGCONN macro, the caller does not have to place any information into any register unless using it in register notation for a particular parameter, or using it as a base register.
Some callers depend on register contents remaining the same before and after issuing a service. If the system changes the contents of registers on which the caller depends, the caller must save them before issuing the service, and restore them after the system returns control.
See the topic on IXG Messages in z/OS MVS System Messages, Vol 10 (IXC-IZP) for more information about IXG messages.
The standard form of the IXGCONN macro is written as follows:
Syntax | Description |
---|---|
name | name: symbol. Begin name in column 1. |
␣ | One or more blanks must precede IXGCONN. |
IXGCONN | |
␣ | One or more blanks must follow IXGCONN. |
Valid parameters (Required parameters are underlined.) | |
REQUEST=CONNECT | All parameters are valid. |
REQUEST=DISCONNECT | STREAMTOKEN, ANSAREA, ANSLEN, USERDATA, RETCODE, RSNCODE, MF |
,STREAMNAME=streamname | streamname: RS-type address or register (2) - (12). |
,STREAMTOKEN=streamtoken | streamtoken: RS-type address or register (2) - (12). |
,ANSAREA=ansarea | ansarea: RS-type address or register (2) - (12). |
,ANSLEN=anslen | anslen: RS-type address or register (2) - (12). |
,AUTH=READ | Default: AUTH=READ |
,AUTH=WRITE | |
,STRUCTNAME=structname | structname: RS-type address or register (2) - (12). |
,AVGBUFSIZE=avgbufsize | avgbufsize: RS-type address or register (2) - (12). |
,MAXBUFSIZE=maxbufsize | maxbufsize: RS-type address or register (2) - (12). |
,ELEMENTSIZE=elementsize | elementsize: RS-type address or register (2) - (12). |
,LSVERSION=lsversion | lsversion: RS-type address or register (2) - (12). |
,USERDATA=userdata | userdata: RS-type address or register (2) - (12). |
,IMPORTCONNECT=NO | Default: IMPORTCONNECT=NO |
,IMPORTCONNECT=YES | |
,DIAG=NO_DIAG | Default: DIAG=NO_DIAG |
,DIAG=NO | |
,DIAG=YES | |
,PLISTVER=IMPLIED_VERSION | |
,PLISTVER=MAX | Default: IMPLIED_VERSION |
,PLISTVER=1 | |
,PLISTVER=2 | |
,RETCODE=retcode | retcode: RS-type address or register (2) - (12). |
,RSNCODE=rsncode | rsncode: RS-type address or register (2) - (12). |
,MF=S | Default: MF=S |
,MF=(L,list addr) | |
,MF=(L,list addr,attr) | |
,MF=(L,list addr,0D) | |
,MF=(E,list addr) | |
,MF=(E,list addr,COMPLETE) | |
,MF=(E,list addr,NOCHECK) | |
,MF=(M,list addr) | |
,MF=(M,list addr,COMPLETE) | |
,MF=(M,list addr,NOCHECK) | |
The parameters are explained as follows:
When you specify CONNECT, all parameters are valid. Keywords required with connect are: STREAMNAME, STREAMTOKEN, ANSAREA, and ANSLEN.
When you specify DISCONNECT, the following parameters are valid (required parameters are underlined): STREAMTOKEN, ANSAREA, ANSLEN, USERDATA, RETCODE, RSNCODE, and MF.
When specified with REQUEST=CONNECT, STREAMTOKEN is an output parameter where IXGCONN places the log stream token when the macro completes successfully.
When specified with REQUEST=DISCONNECT or other logger services, STREAMTOKEN is an input parameter where you specify the log stream token returned at connection.
To ascertain the optimal answer area length, look at the ANSAA_PREFERRED_SIZE field of the IXGANSAA macro.
If you specify AUTH=READ when connecting to a log stream, the program must also have read access authority to SAF resource(logstream_name) in CLASS(LOGSTRM) for the specified log stream. You can then issue only the IXGBRWSE and IXGQUERY requests against the log stream.
If you specify AUTH=WRITE when connecting to a log stream, the program must also have write access authority to SAF resource(logstream_name) in CLASS(LOGSTRM) for the specified log stream. You can then issue any system logger request against the log stream.
If you are connecting to a DASD-only log stream, this field will contain binary zeros. In addition, flag Ansaa_DasdOnlyLogStream in macro IXGANSAA will be set on for a DASD-only log stream.
MAXBUFSIZE is defined in the LOGR policy.
If you are connecting to a DASD-only log stream, this field will contain binary zeros. In addition, flag Ansaa_DasdOnlyLogStream in macro IXGANSAA will be set on for a DASD-only log stream.
The log stream version is a UTC timestamp that uniquely identifies the instance of the log stream definition. A program can use the log stream version to see if a log stream definition has been deleted and redefined since the last connect to a log stream.
For example, assume you connect to log stream LS1 and IXGCONN returns a log steam version of X'AA00000000000000', which the program saves. On a subsequent connection to log stream LS1, IXGCONN returns a different log stream version, which indicates that the definition for log stream LS1 in the LOGR policy has been deleted and redefined since the last connection.
When specified with REQUEST=CONNECT, USERDATA is an output parameter where IXGCONN returns the user data specified for this log stream.
When specified with REQUEST=DISCONNECT, USERDATA is an input parameter where you can specify or update the user data the user data for the specified log stream. You can only specify or change the user data for a log stream on a disconnect request.
If you specify IMPORTCONNECT=YES, this connection will be used for importing data to a log stream. Importing log data means using the IXGIMPRT service to copy data from one log stream to another, maintaining the same log block identifier and UTC time stamp. IXGWRITE requests are not valid with IMPORTCONNECT=YES. You can have only one IMPORTCONNECT=YES connection active for a log stream in the sysplex.
If you specify IMPORTCONNECT=NO, which is the default, the connect request is a write connection. In a write connection, only IXGWRITE requests can be issued against the log stream, IXGIMPRT requests will be rejected.
You can have multiple write connects to a log stream, provided there are no import connections. If you have a write connect established against a log stream, a subsequent import connection will be rejected. You cannot, in other words, issue both IXGIMPRT and IXGWRITE requests against a single log stream.
If you specify DIAG=NO_DIAG, which is the default, then Logger will not provide the additional diagnostics as specified on the logstream definition DIAG parameter, unless another Logger service, for example, IXGBRWSE, specifically requests the additional diagnostics.
If you specify DIAG=NO, the Logger will not provide the additional diagnostics as specified on the logstream definition DIAG parameter, regardless of other Logger service specifications.
If you specify DIAG=YES, then Logger will provide additional diagnostics as specified on the logstream definition DIAG parameter, unless another Logger service, for example, IXGDELET, specifically requests not to provide the additional diagnostics.
If you can tolerate the size change, IBM recommends that you always specify PLISTVER=MAX on the list form of the macro. Specifying MAX ensures that the list-form parameter list is always long enough to hold all the parameters you might specify on the execute form when both forms are assembled using the same level of the system. In this way, MAX ensures that the parameter list does not overwrite nearby storage.
Use MF=L to specify the list form of the macro. Use the list form together with the execute form of the macro for applications that require reentrant code. The list form defines an area of storage that the execute form uses to store the parameters. Only the PLISTVER parameter can be specified on the list form of the macro. IBM recommends that you always specify PLISTVER=MAX on the list form of the macro.
Use MF=E to specify the execute form of the macro. Use the execute form together with the list form of the macro for applications that require reentrant code. The execute form of the macro stores the parameters into the storage area defined by the list form, and generates the macro invocation to transfer control to the service.
Use MF=M together with the list and execute forms of the macro for service routines that need to provide different options according to user-provided input. Use the list form to define a storage area; use the modify form to set the appropriate options; then use the execute form to call the service.
None.
When IXGCONN macro returns control to your program, GPR 15 contains a return code and GPR 0 contains a reason code.
The following table contains hexadecimal return and reason codes, the equate symbols associated with each reason code, and the meaning and suggested action for each return and reason code.
Return Code | Reason Code | Meaning and Action |
---|---|---|
00 | xxxx0000 | Equate Symbol: IxgRsnCodeOk Explanation: Request processed successfully. |
04 | xxxx0404 | Equate Symbol: IxgRsnCodeDisconnectInProgress Explanation: Environment error. The disconnect request is being completed asynchronously. The application has been disconnected from the log stream and the stream token is no longer valid. Action: The log stream cannot be deleted until the asynchronous portion of the disconnect processing completes. |
04 | xxxx0406 | Equate Symbol: IxgRsnCodeConnectRebuild Explanation: Environment error. The connect request was successful, but the log stream is temporarily unavailable because a coupling facility structure re-build is in progress. Action: Listen to the ENF signal 48, which will indicate either that the log stream is available because the re-build completed successfully or that the log stream is not available because the re-build failed. In the meantime, do not attempt to issue system logger services against the log stream. |
04 | xxxx0407 | Equate Symbol: IxgRsnCodeConnPossibleLossOfData Explanation: Environment error. The request was successful, but there may be log blocks permanently missing between this log block and the one previously returned. This condition occurs when a system or coupling facility fails and not all of the data in the log stream could be recovered. Action: If your application cannot tolerate any data loss, stop issuing system logger services to this log stream, disconnect from the log stream, and reconnect to a new, undamaged log stream. You can continue using the log stream if your applications can tolerate data loss. |
04 | xxxx0408 | Equate Symbol: IxgRsnCodeDsDirectoryFullWarning Explanation: Environment error. The request was successful, but the DASD data set directory for the log stream is now full. system logger cannot offload any further data to DASD. system logger will continue to process IXGWRITE requests only until the coupling facility structure space for this log stream is full. Action: Either delete data from the log stream to free up space in the data set directory or disconnect from the log stream. |
04 | xxxx0409 | Equate Symbol: IxgRsnCodeWowWarning Explanation: Environment error. The request was successful, but an error condition was detected during a previous offload of data. system logger might not be able to offload further data. system logger will continue to process IXGWRITE requests only until the interim storage for the log stream is filled. (Interim storage is the coupling facility for a coupling facility log stream and local storage buffers for a DASD-only log stream.) Action: Do not issue any further requests for this log stream and disconnect. Connect to another log stream. Check the system log for message IXG301I to determine the cause of the error. If you cannot fix the error, search problem reporting data bases for a fix for the problem. If no fix exists, contact the IBM Support Center. |
08 | xxxx0801 | Equate Symbol: IxgRsnCodeBadParmlist Explanation: Program error. The parameter list could not be accessed. Action: Ensure that the storage area for the parameter list is accessible to the system logger for the duration of the request. The parameter list storage must be addressable in the caller's primary address space and in the same key as the caller. |
08 | xxxx0802 | Equate Symbol: IxgRsnCodeXESError Explanation: System error. A severe cross-system extended services (XES) error has occurred. Action: See ANSAA_DIAG1 for the XES return code and ANSAA_DIAG2 for the XES reason code. |
08 | xxxx0806 | Equate Symbol: IxgRsnCodeBadStmToken Explanation: Program error. The stream token was not valid. Action: Make sure that the stream token specified is valid. |
08 | xxxx0808 | Equate Symbol: IxgRsnCodeEIOError Explanation: System error. A severe log data set I/O error has occurred. Action: Contact the IBM Support Center. Provide the return and reason code. |
08 | xxxx080A | Equate Symbol: IxgRsnCodeRequestLocked Explanation: Program error. The program issuing the request is holding a lock. Action: Ensure that the program issuing the request is not holding a lock. |
08 | xxxx080B | Equate Symbol: IxgRsnCodeNoStream Explanation: Program error. The log stream name specified has not been defined in the LOGR policy. Action: Ensure that the required log stream name has been defined in the LOGR policy. If the definition appears to be correct, ensure that the application is passing the correct log stream name to the service. |
08 | xxxx080C | Equate Symbol: IxgRsnCodeStagingAllocError Explanation: Environment error. The system encountered a severe dynamic allocation error with the staging data set. ANSAA_DIAG2 of the answer area contains either the dynamic allocation error code, SMS reason code, or media manager reason code. For more information about the error, check for either message IXG251I, which is issued for data set allocation errors, or check for messages issued by the access method. Action: If the problem persists, search problem reporting data bases for a fix for the problem. If no fix exists, contact the IBM Support Center. |
08 | xxxx080D | Equate Symbol: IxgRsnCodeNoSAFAuth Explanation: Environment error. The user does not have correct SAF authorization for the request. The caller is not authorized to connect to the log stream or the caller specified AUTH=WRITE when connecting to a log stream with only READ authority. Action: IXGCONN returns
information about the error in the answer area that is mapped by IXGANSAA.
Investigate the meaning of ANSAA_Diag1, ANSAA_Diag2 and ANSAA_Diag4.
Define the required SAF authorization to allow the requestor to connect to the log stream. If authorization has already been defined, either change the authorization to allow UPDATE access to the log stream or change the application to AUTH=READ. |
08 | xxxx0811 | Equate Symbol: IxgRsnCodeBadStrname Explanation: Environment error. The structure name specified on the STRUCTNAME parameter is not defined in the CFRM policy. Action: Make sure that the structure you want to specify is defined in the CFRM policy. |
08 | xxxx0812 | Equate Symbol: IxgRsnCodeLogStreamRecoveryFailed Explanation: Environment error. The log stream could not be recovered so the connection attempt failed. The system issues message IXG210E and/or IXG211E along with message IXG231I providing further information about the error. Action: If the problem persists, search problem reporting data bases for a fix for the problem. If no fix exists, contact the IBM Support Center. |
08 | xxxx0813 | Equate Symbol: IxgRsnCodeLogStreamDeleted Explanation: Environment error. The request to connect to the specified log stream failed because the log stream is being deleted. Action: Re-define the log stream in the LOGR policy and then re-issue the connect request. |
08 | xxxx0814 | Equate Symbol: IxgRsnCodeNotAvailForIPL Explanation: Environment error. The system logger address space is not available for the remainder of this IPL. The system issues messages about this error during system logger initialization. Action: See the explanation for system messages issued during system logger initialization. |
08 | xxxx0815 | Equate Symbol: IxgRsnCodeNotEnabled Explanation: Program error. The program issuing the request is not enabled for I/O and external interrupts, so the request fails. Action: Make sure the program issuing the request is enabled for I/O and external interrupts. |
08 | xxxx0816 | Equate Symbol: IxgRsnCodeBadAnslen Explanation: Program error. The answer area length (ANSLEN parameter) is not large enough. The system logger returned the required size in the Ansaa_Preferred_Size field of the answer area, mapped by IXGANSAA macro. Action: Re-issue the request, specifying an answer area of the required size. |
08 | xxxx0819 | Equate Symbol: IxgRsnCodeSRBMode Explanation: Program error. The calling program is in SRB mode, but task mode is the required dispatchable unit mode for this system logger service. Action: Make sure the calling program is in task mode. |
08 | xxxx081A | Equate Symbol: IxgRsnCodeMaxStreamConn &
IXGINVNT requests Explanation: Environment error. This system
has reached the limit for the maximum number of log streams that can
be concurrently active. One of the following is true:
Action: Your workload need to be planned to either consolidate log streams or balance system activity such that fewer log streams are needed during this time frame. |
08 | xxxx081B | Equate Symbol: IxgRsnCodePrimaryNotHome Explanation: Program error. The primary address space does not equal the home address space. Action: Make sure that the primary address space equals the home address space when issuing this system logger service. |
08 | xxxx081D | Equate Symbol: IxgRsnCodeRMNameBadState Explanation: Program error. The calling program cannot issue IXGCONN with the RMNAME parameter unless it is in supervisor state and system key. Action: Make sure the calling program is in supervisor state. |
08 | xxxx081E | Equate Symbol: IxgRsnCodeXESStrNotAuth Explanation: Environment Error. The system logger address space does not have access authority to the coupling facility structure associated with the log stream specified. Action: Make sure the system logger address space has SAF access to the structure. |
08 | xxxx081F | Equate Symbol: IxgRsnCodeXcdsError Explanation: System error. system logger encountered an internal problem while processing the LOGR couple data set. Action: Contact the IBM Support Center. Provide the return and reason code and the contents of the answer area (ANSAREA field). |
08 | xxxx0820 | Equate Symbol: IxgRsnCodeBadModelConn Explanation: Program error. The program issued an IXGCONN request to connect to a log stream that was defined as a model in the LOGR policy. You cannot connect to a model log stream. Action: Either change the definition of the specified structure so that it is not a model, or else request connection to a different log stream that is not a model. |
08 | xxxx082D | Equate Symbol: IxgRsnCodeExpiredStmToken Explanation: Environment error. The stream token is no longer valid because the connector has been disconnected. Action: Connect to the log stream again before issuing any functional requests. |
08 | xxxx082E | Equate Symbol: IxgRsnCodeNoLogrCDSAvail Explanation: Environment error. The request failed because no LOGR couple data set is available. The operator was prompted to either make a couple data set available or to indicate that the current request should be rejected. The operator specified that the current request should be rejected. Action: system logger services are unavailable for the remainder of this IPL. |
08 | xxxx0831 | Equate Symbol: IxgRsnCodeBadStreamName Explanation: Program error. The log stream name specified on the STREAMNAME parameter is not valid. Action: Issue the request again with a valid log stream name on the STREAMNAME parameter. |
08 | xxxx083A | Equate Symbol: IxgRsnCodeRMNameNotAllowed Explanation: Program error. The request specified the RMNAME parameter, but the log stream is not defined as having an associated resource manager. Action: Either define a resource manager for the log stream definition in the LOGR couple data set, or remove the RMNAME parameter from the request. |
08 | xxxx0843 | Equate Symbol: IxgRsnCodeXcdsReformat Explanation: Program error. A couple data set record is not valid. Action: Format the system logger couple data set again. |
08 | xxxx084C | Equate Symbol: IxgRsnCodeRMAlreadyConnected Explanation: Program error. The resource manager is trying to connect to a log stream that it is already connected to. Only one connection specifying RMNAME can be active for a log stream. Action: Correct the program so that it does not try to reconnect to the log stream. |
08 | xxxx084E | Equate Symbol: IXGRSNCODESTRSACETOOSMALL Explanation: Environment error. Structure resources are not available to satisfy the request. All structure resources are allocated as system logger control resources. This condition occurs when the structure resources are consumed by the logstreams connections. Action: Increase the size of the structure in the CFRM policy or use SETXCF ALTER support to dynamically increase the size of the structure. |
08 | xxxx084F | Equate Symbol: IxgRsnCodeInvalidRMNameSpecified Explanation: Program error. The value for the RMNAME parameter on the connect request does not match the name of the resource manager defined in the LOGR couple data set for the log stream. Action: Either correct the RMNAME value on the connect request or correct the resource manager name in the log stream definition in the LOGR couple data set. |
08 | xxxx0850 | Equate Symbol: IXGRSNCODEBADVECTORLEN Explanation: Environment error. The connect request was rejected. system logger was unable to locate a vector table in the hardware system area (HSA) that is large enough for the number of log streams associated with it. Action: Add storage to the vector storage table and/or retry the connect request later, when storage might be available. |
08 | xxxx0851 | Equate Symbol: IXGRSNCODEBADCFLEVEL Explanation: Environment error. The connect request was rejected. The operational level of the coupling facility is not sufficient to support logger functions. Action: Ensure that the coupling facility operational level for logger structures is at the required level. See z/OS MVS Setting Up a Sysplex. |
08 | xxxx0853 | Equate Symbol: IxgRsnCodeNoCF Explanation: Environment error. The connect request was rejected. system logger could not allocate coupling facility structure space because no suitable coupling facility was available. Action: Check accompanying message IXG206I for a list of the coupling facilities where space allocation was attempted and the reason why each attempt failed. |
08 | xxxx0861 | Equate Symbol: IxgRsnCodeRebuildInProgress Explanation: Environment error. No requests can be processed for this log stream because a coupling facility structure re-build is in progress for the structure associated with this log stream. Action:
Listen for ENF signal 48 that will indicate one of the following:
|
08 | xxxx0862 | Equate Symbol: IxgRsnCodeXESPurge Explanation: Environment error. An cross-system extended services (XES) request has been purged due to re-build processing. Action:
Listen for ENF signal 48 that will indicate one of the following:
|
08 | xxxx0863 | Equate Symbol: IXGRSNCODESTRUCTUREFAILED Explanation: Environment error. Either the coupling facility structure associated with the log stream has failed or the coupling facility itself has failed. Action: Listen for ENF signal 48 that will indicate
one of the following:
|
08 | xxxx0864 | Equate Symbol: IXGRSNCODENOCONNECTIVITY Explanation: Environment error. No connectivity exists to the coupling facility associated with the log stream. The system logger will either attempt to re-build the log stream in another coupling facility or the log stream will be disconnected. Action: Listen for ENF
signal 48 that will indicate one of the following:
If a re-build initiated because of a loss of connectivity previously failed, an ENF corresponding to this reason code might not be issued. Further action by the installation might be necessary to cause the change of the log stream status again. Check the log for messages IXG101I, IXG107I and related rebuild messages for information on resolving any outstanding issues. |
08 | xxxx0866 | Equate Symbol: IXGRSNCODESTRUCTUREFULL Explanation: Environment error. The coupling facility structure space is full. Action: Listen to the ENF signal 48 which will indicate that space is available for the structure after data has been offloaded to DASD. |
08 | xxxx0890 | Equate Symbol: IXGRSNCODEADDRSPACENOTAVAIL Explanation: System error. The system logger address space failed and is not available. Action: Do not issue system logger requests. |
08 | xxxx0891 | Equate Symbol: IXGRSNCODEADDRSPACEINITIALIZING Explanation: System error. The system logger address space is not available because it is IPLing. Action: Listen for ENF signal 48, which will indicate when the system logger address space is available. Re-issue this request. You can also listen for ENF signal 48, which will indicate if the system logger address space will not be available for the life of the IPL. In that case, do not issue system logger services. |
08 | xxxx08B0 | Equate Symbol: IXGRSNCODESTRUCTURENOTAVAIL Explanation: Environment error. The connect request failed. The structure associated with the log stream is temporarily unavailable because either a re-build is in progress, a structure dump is in progress, or connections to the structure are being prevented. Action: Listen for ENF signal 48, which indicates that a coupling facility is available, and then retry the connect. |
08 | xxxx08D3 | Equate Symbol: IXGRsnCodeFuncNotSupported Explanation: Environment error. The connect request specified the RMNAME or IMPORTCONNECT parameter. The request failed because the active primary LOGR couple data set must be at the z/OS level to support these parameters. Action: Either retry the request without the RMNAME or IMPORTCONNECT parameters or reformat the LOGR couple data set to the z/OS level. |
08 | xxxx08D6 | Equate Symbol: IXGRsnCodeConnTypeNotAllowed Explanation:
Environment error. One of the following occurred:
You can only have one import connection to a log stream. You may have multiple write connections, as long as there is no import connection against a log stream. Action: Correct your program and retry the request. |
08 | xxxx08E2 | Equate Symbol: IxgRsncodeDasdOnlyConnected Explanation: Environment error system logger rejected an attempt to connect to a DASD-only log stream because the log stream is already connected to by another log stream in the sysplex. Only one system at a time can connect to a DASD-only log stream. Action: Determine which system you want to have a connection to the log stream. If you need this connection, disconnect the first system connection to the log stream and retry this connect request. |
08 | 000008E3 | Equate Symbol: IxgRsnCodeLogstreamNotSupported Explanation: Environment error. An attempt to connect for the log stream is rejected on this system because the system release level does not support this type of log stream. For example, this system does not support DASD-only log streams, or a log stream attribute such as EHLQ or DUPLEXMODE(DRXRC) cannot be processed on this system release level. Action:
If you must connect to a DASD-only log stream, make sure you do one
of the following:
If you must connect to a log stream with the EHLQ attribute specified, make sure you connect from a system that is at z/OS Version 1 Release3 or higher. If you must connect to a log stream with the DUPLEXMODE(DRXRC) attribute specified, make sure you connect from a system that is at z/OS Version 1 Release 7 or higher. |
0C | xxxx0000 | Equate Symbol: IxgRetCodeCompError Explanation:
User or System error. One of the following occurred:
Action: If this reason code is not the result of forcing the system logger address space, search problem reporting data bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the diagnostic data in the answer area (IXGANSAA) and any dumps or LOGREC entries from system logger. |
IXGCONN REQUEST=CONNECT, X
STREAMNAME=STRMNAME, X
STREAMTOKEN=TOKEN, X
AUTH=WRITE, X
ANSAREA=ANSAREA, X
ANSLEN=ANSLEN, X
RSNCODE=RSNCODE, X
MF=S, X
RETCODE=RETCODE
STRMNAME DC CL26'LOG.STREAM.NAME' stream name
ANSLEN DC A(L'ANSAREA) length of logger's answer area
TOKEN DS CL16 returned stream token
ANSAREA DS CL(ANSAA_LEN) answer area for log requests
RETCODE DS F return code from logger
RSNCODE DS F reason code from logger
DATAREA DSECT
IXGANSAA LIST=YES answer area
LA R6,STRMNAME load stream name into reg 6
IXGCONN REQUEST=CONNECT, X
STREAMNAME=(6), X
STREAMTOKEN=TOKEN, X
AUTH=WRITE, X
ANSAREA=ANSAREA, X
ANSLEN=ANSLEN, X
RSNCODE=RSNCODE, X
MF=S, X
RETCODE=RETCODE
STRMNAME DC CL26'LOG.STREAM.NAME' stream name
ANSLEN DC A(L'ANSAREA) length of logger's answer area
TOKEN DS CL16 returned stream token
ANSAREA DS CL(ANSAA_LEN) answer area for log requests
RETCODE DS F return code from logger
RSNCODE DS F reason code from logger
DATAREA DSECT
IXGANSAA LIST=YES answer area
R6 EQU 6 set up register 6
IXGCONN REQUEST=CONNECT, X
STREAMNAME=ONAME, X
STREAMTOKEN=OTOKEN, X
AUTH=WRITE, X
IMPORTCONNECT=YES, X
ANSAREA=XANSAREA, X
ANSLEN=XANSLEN, X
RSNCODE=RSCODE
*
ONAME DS CL26 Output Stream name
STOKEN DS CL16 Input Stream token
XANSAREA DS CL(ANSAA_LEN) Logger answer area
XANSLEN DC A(ANSAA_LEN) Answer area length
RSCODE DS F Reason code
DSECT ,
IXGANSAA , The answer area macro
IXGCONN REQUEST=DISCONNECT, X
STREAMTOKEN=TOKEN, X
USERDATA=USERDATA, X
ANSAREA=ANSAREA, X
ANSLEN=ANSLEN, X
RSNCODE=RSNCODE, X
MF=S, X
RETCODE=RETCODE
USERDATA DC CL64'SOME USER DATA' user data to log with DISCONNECT
ANSLEN DC A(L'ANSAREA) length of logger's answer area
TOKEN DS CL16 token returned from CONNECT
ANSAREA DS CL(ANSAA_LEN) answer area for log requests
RETCODE DS F return code from logger
RSNCODE DS F reason code from logger
DATAREA DSECT
IXGANSAA LIST=YES answer area