|
Folks: JBakerii@aol.com wrote: > > > The PTF's are SF42454 and SF42455. We are on V3R2, and were currnet with all > PTF's as far as we knew. I have not seen the cover letters for these PTF's, > but the operations supervisor say they cover a lot of stuff. I reproduce portions of the cover letter below. Seems like a very dangerous mission critical problem resolution. I am getting the PTFs and applying pronto. A variety of problems have occurred whereby the indication is that certain objects on the system are corrupted. The origin of the corruption has been linked to the termination of query requests which were implemented with either or both of UNION and/or SORT temporary results. The termination can be by an ENDRQS, ENDJOB, or a VLIC function check; meaning the termination was abnormal rather than a clean-exit. More keywords for problem origin: SYSREQ-2 SYSREQ2 ENDRQS CANCEL QRY OPNQRYF STRQMQRY SQL SQLRUN QRYRUN RUNQRY WRKQRY STRSQL STRQM PRTDSKINF QRY400 QUERY400 MSGMCH3203 RC1716 or RC0306 or RC0307 typically MCH3203 F/#CFASUME T/QDBGETM X/0296 Many times the problem will produce an extended joblog of sometimes thousands of pages of errors in programs QQQQEXIT, QQQTSORT, QDMCLOSE, and QDMERRHP. During this time the system may encounter a joblog wrapped or job terminated due to job message queue full condition, plus sometimes several VLIC function check VLogs for the errors encountered. More keywords for typical conditions after problem origin: VL02000306 IXPTN18 IAR1ABE x/1ABE T/QQQQEXIT TIDYUP VL02000306 IXPTN18 IAR051C x/051C T/QDMERRHP X/0012 See MSGMCH3402 T/QDMCLOSE MSGCPF2524 &MSGCPF4510 plus some MSGMCH0606 and a MSGMCH4407 F/#DOMTINA sometimes in VLogs. Often following the error will be VL06001C85 for #DBCDSEH albeit an innocuous condition. Symptoms of corruption are listed by the type of corruption. >> System value corruption **note** A problem with system value corruption had been reported and supposedly solved by changes to some query PTFs which added new system values during V3R1M0. This is _not_ that problem; though that problem may have really been this problem. The most common system value corruption was with QUSRLIBL whereby the library name QGPL became QgPL or QGpL; and too for any other library in the list. The corruption problem is generally a lower case letter <when expected to be upper case>. The spooled joblog for SCPF shows the condition of MSGMCH3401 F/#MNRCTX x'0401' which then effects MSGCPF0987 F/QWCISCFR T/QSYSOPR during the IPL. Similarly this could occur for QSYSLIBL effecting MSGCPF0985 instead during IPL. More keywords for system value corruption: LOWERCASE UPPERCASE BITON BITOFF SYSVAL QWMSYSVAL DSPSYSVAL WRKSYSVAL CHGSYSVAL MSGCPF1030 attempting to correct a system value for which change is not supported Other system values believed to have been affected by this problem <not meaning to imply these are the only possible>, but for which additional symptoms have not been noted, but for which keywords can be searched: QAUDLVL QCONSOLE <eg. as DjP01> QMODEL >> Associated space of system program QDMCOPEN corrupted After this corruption there may be many failures to open device files, all with the symptoms below. ..... many more pages after this.... -- Thank You. Regards Dave Mahadevan.. mailto:mahadevan@fuse.net +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to "MIDRANGE-L@midrange.com". | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.