|
Thanks Justin. No changes this weekend on that machine. Last IPL was August 23. V5R2 cume=TL03161 WRKPTFGRP PTF Group Level SF99519 71 SF99502 8 SF99271 9 SF99169 13 SF99149 3 SF99148 3 SF99098 10 SF99085 6 SF99039 2 And as far as I am aware, no network changes. I have opened up a pmr on the WRKLICINF. I might as well open one on this too. Rob Berendt -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin "Justin C. Haase" <JHaase@xxxxxxxxxxxxx> Sent by: midrange-l-bounces@xxxxxxxxxxxx 09/22/2003 10:06 AM Please respond to Midrange Systems Technical Discussion To: "'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx> cc: Fax to: Subject: RE: QINTER problems: CPF5390, CPF1317, CPF1189, CPF1196 With the earlier comment about WRKLICINF blowing up and now your interactive/comms are blowing up too, I think it would probably be best to get IBM on the horn before the whole thing goes on you. Were there any changes this weekend? Stuff like this doesn't usually just come about. What OS version are you at? PTFs? Recent IPL? Network changes? jch -----Original Message----- From: rob@xxxxxxxxx [mailto:rob@xxxxxxxxx] Sent: Monday, September 22, 2003 10:02 AM To: MIDRANGE-L@xxxxxxxxxxxx Subject: QINTER problems: CPF5390, CPF1317, CPF1189, CPF1196 One person had their interactive job message with CPF1317-Message . . . . : No response from subsystem for job jobnbr/jobuser/jobname. Cause . . . . . : The subsystem failed to respond to a user request within the job default wait time limit. The amount of the function completed by the subsystem cannot be determined. This message may occur if this job default wait time is too small or if the subsystem that the job is running in is unavailable to respond to the request. Also noticed the following in QSYSOPR regarding another job around that same time: CPF1189-Subsystem QINTER varied off work station (wsid). Cause . . . . . : Subsystem QINTER received CPF5390 while using file QDSIGNON in library ROUTINES record format SIGNON. As a result of this error, work station (wsid) was varied off by the subsystem. dspmsgd cpf5390 is interesting Lots of strange messages when I look at the joblog for subsystem QINTER: ... Not able to transmit to device PAPC3S7. Session not in send condition. Input or Output request failed. See message CPF5423. This message used internally only by display function manager. Device PAPC3S7 is no longer assigned to the program. Restore request failed. See message CPF5217. Restore request failed. See message CPF5217. I Device PAPC3S7 is no longer assigned to the program. Lock enforcement rules broken when trying to access object PAPC3S7. Function check. MCH2601 unmonitored by QWSRSCRC at statement *N, instruction X'0045'. Failure for device or member *N file *N in library *N. Subsystem QINTER trying to recover work station PAPC3S7. Dequeue operation not satisfied in 126 seconds for queue QMIRQ Time-out occurred during input or output, device PAPC3S2 failed. Device CLL3S1 session not active. Subsystem QINTER trying to recover work station CLL3S1. Device BILLMOS1 session not active. Subsystem QINTER trying to recover work station BILLMOS1. Device PAPC3S2 not varied off. Error occurred. Vary command not processed. Subsystem QINTER varied off work station PAPC3S2. Subsystem QINTER failed to vary off device PAPC3S2. ... DSPSBSD QINTER Subsystem description . . . . . . . . : QINTER Library . . . . . . . . . . . . . . : QSYS Maximum jobs in subsystem . . . . . . : *NOMAX Sign-on display file . . . . . . . . . : QDSIGNON Library . . . . . . . . . . . . . . : ROUTINES System library list entry . . . . . . : *NONE DSPFD ROUTINES/QDSIGNON ... Maximum record wait time . . . . . . . . . : WAITRCD *NOMAX ... DSPJOB of job that had error: Default wait time in seconds . . . . . . . . . . : 30 Where do I go with this one? Rob Berendt -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
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.