OA67194: CREATE A _V3 VERSION OF THE CA10 AND CA20 DATA TYPES.

APAR status

• Closed as duplicate of another APAR.

Error description

• Customer states has missing 34 bytes of data since z/OS Connect
  has a 64 byte field for the tracking token and he only sees 30
  bytes of actual data. The CDP definition for the CA10 is in
  HBORSIMS. The part dealing with the token is:
  
  ZOSPFX   LENGTH 4 HEX,           -- z/OS Connect Tracking token
  ZOSLEN   LENGTH 2 BINARY,        -- z/OS token length
  ZOSPLEX  LENGTH 8 CHAR,          -- z/OS SYSPLEX name
  ZOSSYSN  LENGTH 8 CHAR,          -- z/OS SYSTEM name
  ZOSSTCK  LENGTH 8 HEX,           -- z/OS Token (STCK)
  *        LENGTH 34 HEX,
  The customer included the record:
  C2C1D8010018D4E5E2E3C5E2E340D6E2E3F240404040DFCF2EB13E984BA0004
  0404040404040404040404040404040404040404040404044040404040404040
  
  Breaking it out with the above structure it looks like:
  
  
  ZOSPFX      C2 C1 D8 01
  ZOSLEN      00 18     -- z/OS token length
  ZOSPLEX     D4 E5 E2 E3 C5 E2 E3 40
  ZOSSYSN     D6 E2 E3 F2 40 40 40 40
  ZOSSTCK     DF CF 2E B1 3E 98 4B A0
  The token length field is 00 18 hex or 24 decimal, which matches
  the length of the next 3 fields. So, the data is saying the
  token only includes the next 24 bytes, it appears the CDP is
  correct to ignore the following 34 bytes.
  
  The z/OS Connection documentation states it will pad the
  tracking token field with spaces if the token provided is not 64
  bytes.  This is why he is seeing the 34 bytes of 0x40 tacked on
  the end of the first 30 bytes of data. See:
  
  https://www.ibm.com/docs/en/zos-connect/zosconnect/3.0?topic=us
  rmr-api-provider-data-from-smf-type-1231-v2-records#smf_provide
  r_v2__tracking_token
  
  SMF123S1_TRACKING_TOKEN              64           BINARY
        Tracking token that is padded with spaces (0x40) since
  V3.0.45 and nulls (0x00) previously. See Note 3.
  
  
  CDP can create a new field for this, but we will have to
  create a _V3 version of the CA10 and CA20 data types.
  

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

• Fixed in OS67137
  This APAR is a duplicate of OA67137
  

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels