|
IMS PI 230
|
|||||
| APAR | CLOSE DATE |
PTF(s) | Fixing APAR if PE |
HIPER? | Abstract |
|---|---|---|---|---|---|
2015 |
INVALID RESULTS IN BROWSE DISPLAY AFTER ISSUING TX COMMAND | ||||
2015 |
IMS PSUEDO-ABEND CODE IN THE IMS X'67FF' RECORD INCORRECTLY DISPLAYED IN THE ABEND GLOBAL FIELD | ||||
2015 |
RANDOM ABENDS (S0C4, S0C6) PROCESSING IMS V13 LOG WITH RECORDS CONTAINING COMPRESSED DATA | ||||
2015 |
MULTIPLE ISSUES ADDRESSED: IMS CONNECT LOG RECORD CODE NOT PROVIDED AS NEEDED AND UPDATES TO KNOWLEDGE MODULES | ||||
2015 |
SUPPORT CHANGES IN X'CA01' TRANSACTION INDEX ADDED BY PI32321 AND SUPPORT IMS SERVICE CHANGES IN SUNDRY KNOWLEDGE MODULES | ||||
2014 |
OTMA SECURITY DATA NOT BEING FORMATTED CORRECTLY | ||||
2014 |
IMS X'4084' AND X'9904' RECORDS ARE BEING INCORRECTLY FORMATTED | ||||
2014 |
ABEND0C4 IN IMS KNOWLEDGE MODULE ALZ30C AT X'34B0' | ||||
2014 |
ABEND0C7 COMCSUTC X'22C' WHEN INCORRECT IMS VERSION IS USED AND ROLL-UP OF INTERNAL ISSUES - SEE ERROR DESC FOR DETAILS | ||||
2014 |
IMS X'6740' RECORD NOT INCLUDED IN A TRACKING RESULT SET | ||||
2014 |
MESSAGE "ALZ0111E UNRECOVERABLE LOGICAL IO ERROR 6" RECEIVED WHEN BROWSING WITH FILTER | ||||
2014 |
IMS X'99' LOG RECORD INCORRECTLY FORMATTED | ||||
2014 |
IMS LOG TYPE X'6705' DMSG SECTION FORMATTED INCORRECTLY | ||||
2014 |
SOME TIME FIELDS WITH A STCK FORMAT IN THE LOG RECORD ARE NOT BEING FORMATTED CORRECTLY IN CSV DATA SETS | ||||
2014 |
AE APAR TO CORRECT UI19324 | ||||
2014 |
SOME GLOBAL FIELDS MAY NOT BE CORRECTLY DISPLAYED WHEN BROWSING AN IMS LOG | ||||
2014 |
IMS PI DOES NOT FORMAT THE CONTENTS OF OMHDCRHQ_TPIPEN AS A TIMESTAMP IN ZOOM MODE WHEN IT CONTAINS A STCK TOKEN | ||||
2014 |
ABENDS0C4 ALZBRCA + X'ABE' | ||||
2014 |
ABEND0C4 IN KNOWLEDGE MODULE CALLED FROM ALZBRAPI X'34F2' USING FIND COMMAND IN LOG BROWSE | ||||
2014 |
IMS X'2931' RECORD IS NOT RECOGNIZED | ||||
2014 |
PROVIDE ENHANCEMENT TO APAR PI06503 WHICH SUPPLIED SUPPORT OF IMS V13 CONNECT TWO BYTE EVENT CODES | ||||
2014 |
ADJUST HANDLING OF IMS LOG TYPE X'6701' AND X'4040' RECORDS IN CERTAIN CASES | ||||
2013 |
IMS V13 SUPPORT | ||||
2013 |
DB2 RECORDS IN A DYNAMIC EXTRACT FILE ARE NOT CORRECTLY IDENTIFIED AND ARE PROCESSED AS IMS RECORDS | ||||
2013 |
FINDLIM SETTING IN IMS PI MAY INFLUENCE TRACKING RESULT SET | ||||
2013 |
USING THE IMS PI TIME-OF-DAY FUNCTION IT SOMETIMES TAKES TWO PASSES TO LOCATE THE REQUIRED RECORD/POSITION IN THE FILE | ||||
2013 |
IMS PI TRACKING MAY INCORRECTLY INCLUDE RECORDS IN A RESULT SET THAT HAVE ORIGINATED FROM, OR ARE TO BE SENT TO MQSERIES | ||||
2013 |
TRACK FORWARD / BACK COMMANDS NOT AVAILABLE IN IMS PI V2.3 | ||||
2013 |
ABEND0C1 FROM ROUTINE ALZ01B | ||||
2013 |
MSGALZ0111E PROCESSING IMS LOG THAT CONTAIN TYPE X'6701' RECORDS | ||||
2013 |
SUPPORT FOR IMS AND CEX SERVICE UPDATES | ||||
2013 |
IMS TRACE ENTRY X'5D03' UNFORMATTED WHEN BROWSING SLDS AND TWO OTHER ISSUES BEING ADDRESSED | ||||
2013 |
SUPPORT SUBCODES OF THE IMS LOG RECORD TYPE 50 | ||||
2013 |
IMS PI V230 INCLUDES KNOWLEDGE MODULE ALIASES FOR UNSUPPORTED IMS RELEASES | ||||
2013 |
CEX EVENT RECORD TYPE 171 AND 172 ARE NOT SUPPORTED | ||||
2013 |
MSGALZ0111E IO ERROR REAS=6 OR REAS=3 RECEIVED PROCESSING IMS V11 SLDS | ||||
2013 |
ERROR MESSAGE ALZ0106E RECEIVED WHEN TRYING TO ACCESS EXTENDED ADDRESS VOLUME (EAV) DATASET | ||||
2013 |
UNRELATED 67FF RECORDS APPEARING IN FAST PATH TRACKING RESULT SET | ||||
2013 |
IMS PROBLEM INVESTIGATOR PRE-CONDITIONING FOR IMS V13 COMPATIBILITY | ||||
2013 |
IMS PROBLEM INVESTIGATOR PRE-CONDITIONING FOR IMS V12 | ||||
2013 |
IMS PROBLEM INVESTIGATOR PRE-CONDITIONING FOR IMS V10 | ||||
2013 |
IMS PROBLEM INVESTIGATOR PRE-CONDITIONING FOR IMS V11 | ||||
2012 |
PRIVATE OTMA USER DATA NOT DISPLAYED | ||||
2012 |
IMSPI PROVIDE NEW ISPF DIALOG COMMANDS TO CONTROL THE DISPLAY OFIMS TRACE EVENTS | ||||
2012 |
PROVIDE SUPPORT FOR UPDATED LOG RECORDS IN IMS V10 V11 V12 | ||||
2012 |
SERVICE ROLLUP FOR IMSPI V2.3 | ||||