A fix is available
APAR status
Closed as program error.
Error description
Applications attempting to use OA38747 new IXGQUERY keyword REQUEST=ZAILOCINFO may encounter a return and reason code of 8/806 indicating a bad streamtoken (even though no streamtoken is specified on the request). This occurs in cases where the application address space does not have a connection to a logstream. This cause of this problem is an error in the routines invoked by IXGQUERY service. The routines expect certain storage areas to be established - these storage areas only are established if a connect to a log stream has occurred. In the problem case, logger detects that these storage areas have not been created, and returns the 8/806 error indication. However, a connection is not required by IXGQUERY REQUEST=ZAILOCINFO. Logger should be modified to recognize this new request, and create required storage areas instead of returning an error indication. Additional Searchable Keywords: E2827/K
Local fix
If you encounter this error for an application being coded to use IXGQUERY REQUEST=ZAILOCINFO, a workaround is to issue a dummy connection request (IXGCONN) to a nonexistant log stream. The connection request will fail, but the necessary storage will be established and the subsequent IXGQUERY REQUEST=ZAILOCINFO will pass the storage checks.
Problem summary
**************************************************************** * USERS AFFECTED: Users of HBB7780 with PTFs for APAR * * OA38747 applied and above supported * * releases using System Logger Service * * IXGQUERY REQUEST=ZAILOCINFO * **************************************************************** * PROBLEM DESCRIPTION: IXGQUERY REQUEST=ZAILOCINFO MAY RETURN * * 8/806 IN ERROR. * **************************************************************** * RECOMMENDATION: * **************************************************************** Logger exploiters using recently added IXGQUERY keyword REQUEST=ZAILOCINFO provided in the enhancements for OA38747 may encounter a return and reason code of 8/806 indicating a bad streamtoken (even though no streamtoken is specified on the request). This occurs in cases where the application address space had not previously performed an IXGCONN REQUEST=CONNECT to a logstream. The logger routines handling the IXGQUERY request expect certain storage areas to be established, and these storage areas only are established if a connect to a log stream had occurred. In the problem case, logger detects that these storage areas have not been created, and returns the 8/806 error indication. Note, a prior log stream connection or any log stream token is not intended to be required by IXGQUERY REQUEST=ZAILOCINFO. Logger should be modified to recognize these circumstances, and create required storage areas instead of returning an error indication when appropriate.
Problem conclusion
The unintended requirement of having a prior IXGCONN REQUEST=CONNECT occur for an application address space before issuing an IXGQUERY keyword REQUEST=ZAILOCINFO has been removed. As a consequence of the fix for APAR OA41313, when issuing an IXGQUERY REQUEST=ZAILOCINFO, the current primary address space must be the same as the HOME address space, unless a log stream connection (IXGCONN connect) request was previously performed from the same application primary address space instance. This PTF may be applied and activated on one system at a time in the sysplex. Systems with and without the fix activated can coexist in the same sysplex, although the problem may persist on those systems running without the fix. Additional Searchable keywords: SYSPLEXDS IBM.Device.Server.zEC12-2827.Exploitation ACTION INFO FOR OA41313 **************************************************************** * FUNCTION AFFECTED: BCP (OA41313) * * Logger * * External Interfaces * * IXGQUERY * **************************************************************** * DESCRIPTION : Other * **************************************************************** * TIMING : Post-APPLY * **************************************************************** Logger APAR OA38747 enabled the z/OS IBM zAware log stream client support on z/OS v1r13. Included in the enhancements was an additional function for the logger service IXGQUERY REQUEST=ZAILOCINFO to return the ZAI SERVER and PORT information from the logger IXGCNFxx parmlib specifications. The correction for the issue identified in APAR OA41313 results in an update to the programming requirements when using the ZAILOCINFO specification. Ensure any program coding REQUEST=ZAILOCINFO on an IXGQUERY invocation meets the requirement of the current primary address space being the same as the HOME address space, unless a log stream connection (IXGCONN connect) request was previously performed from the primary address space. DOCUMENTATION INFO FOR OA41313 **************************************************************** * FUNCTION AFFECTED: BCP (OA41313) * * Logger * * External Interfaces * * IXGQUERY * **************************************************************** * DESCRIPTION : Documentation updates * **************************************************************** * TIMING : As Needed * **************************************************************** Summary of changed Publications -- z/OS V1R13 MVS Programming: Assembler SA22760113 Services Reference, Vol 2 (IARR2V - XCTLX) IXGQUERY - Query a log stream or system logger information Programming requirements o When coding REQUEST=ZAILOCINFO: + - The current primary address space must be the same as + the HOME address space, unless a log stream connection + (IXGCONN connect) request was previously performed from + the primary address space. - Include mapping macro IXGQZBUF in your program. This macro shows the format of the data returned by this IXGQUERY. Return and reason codes Return Reason Meaning Code Code and Action + 08 xxxx081B IXGRSNCODEPRIMARYNOTHOME + + Explanation: Program error. The primary address + space does not equal the home address space. + + Action: Either make sure that the primary + address space equals the home address space when + issuing this type of system logger service. Or + perform a log stream connection (IXGCONN + connect) request from the same primary address + space, then reissue the IXGQUERY request.
Temporary fix
Comments
APAR Information
APAR number
OA41313
Reported component name
SYSTEM LOGGER
Reported component ID
5752SCLOG
Reported release
780
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
YesSpecatt / SYSPLXDS
Submitted date
2013-01-30
Closed date
2013-03-26
Last modified date
2013-10-04
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UA68452
Modules/Macros
IXGCON IXGC2CON IXGC3CON IXGF2QRY IXGL1RTE IXGL2RTE IXGQUERY
SA22760113 |
Fix information
Fixed component name
SYSTEM LOGGER
Fixed component ID
5752SCLOG
Applicable component levels
R780 PSY UA68452
UP13/04/10 P F304
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"780","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":null,"label":null},"Product":{"code":"SG19O","label":"APARs - MVS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"780","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
04 October 2013