Rob,
1) Yes, I changed my normal session from PALPR5580N to point to PALPR5641F.
2) Correct.
3) WRKOBJLCK showed no locks.
I did a scan of all joblogs, looking for all CPF2450 starting with 07/01/15.
Found several hits, but only for the two devices/msgq with the issue, PALPR5641D, PALPR5641F, problem started on 7/21.
I then checked for the last joblog for those two sessions last used with no issue, 7/17 and 07/02.
CPF1164 Completion 00 07/17/15 16:30:18.238996 QWTMCEOJ QSYS 014A *EXT *N
Message . . . . : Job 874445/CPAKFRAN/PALPR5641D ended on 07/17/15 at
16:30:18; 3.493 seconds used; end code 0 .
CPF1164 Completion 00 07/02/15 06:20:34.163848 QWTMCEOJ QSYS 014A *EXT
Message . . . . : Job 794509/CPAKFRAN/PALPR5641F ended on 07/02/15 at
06:20:34; 4.469 seconds used; end code 0 .
An IPL for latest CUM and groups was done 7/20/15.
So these two devices/msgqs haven't functioned correctly since the IPL.
I checked QHST for any messages during the IPL for these two devices, nothing here.
At this point, I'm thinking the IPL left either the device and/or associated message q in some weird state, resulting in the CPF2450.
Paul
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Monday, July 27, 2015 2:40 PM
To: Midrange Systems Technical Discussion
Subject: RE: Strange seesion issue - message q issue
Just to clarify...
1 - We're talking this job: PALPR5580N
2 - Which you got to by pointing your communications, configuration to PALPR5641F?
BTW I did some searching on CPF2450 with a from program of QMHCHMSQ. Came up on this list in January and basically that person had the user name same as a workstation issue. Didn't think so at first but it turned out to be true. He changed it to qualify the library name. Which, I wonder if you'd need if you used the generic *WRKSTN.
Anything on WRKOBJLCK?
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
From: "Steinmetz, Paul" <PSteinmetz@xxxxxxxxxx>
To: "'Midrange Systems Technical Discussion'"
<midrange-l@xxxxxxxxxxxx>
Date: 07/27/2015 01:59 PM
Subject: RE: Strange seesion issue - message q issue
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
Rob,
I changed/pointed one of my iSeries Access sessions on my PC to one of the
2 sessions in question. PALPR5641F.
Communication, configure, specify work station ID. PALPR5641F
When a user signs on, there are two messageqs associated with the job,
1) Userprofile message q
2) Device message q.
We are retrieving the name of the device, and then setting the device
messageq to break.
0004.00 DCL VAR(&WSID) TYPE(*CHAR) LEN(10)
0004.02 DCL VAR(&USERID) TYPE(*CHAR) LEN(10)
0005.00 RTVJOBA JOB(&WSID) USER(&USERID)
0005.08 IF COND(&BJA5VN *NE &USERID) THEN(DO)
0005.09 CHGMSGQ MSGQ(&WSID) DLVRY(*BREAK)
Job . . : PALPR5580N User . . : CPAPSTEI Number . . . : 925945
parameters */
500 - RTVJOBA JOB(&WSID) USER(&USERID)
509 - CHGMSGQ MSGQ(PALPR5580N) DLVRY(*BREAK)
This always works without issue.
So, for unknown reasons, the device message was not allocated to this job,
thus resulting in a CPF2450 - Work station message queue &1 not allocated
to job.
Paul
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
rob@xxxxxxxxx
Sent: Monday, July 27, 2015 1:18 PM
To: Midrange Systems Technical Discussion
Subject: Re: Strange seesion issue - message q issue
You say you were able to 'duplicate' the situation by pointing your
session to of the two sessions. Let me try to interpret that statement
(which seems to be missing a noun, among other things).
You did something like
WRKCFGSTS *DEV *VRTDSP
picked one not in use. ran
CHGMSGQ MSGQ(MYWSID) DLVRY(*BREAK)
and got CPF2450. Well, if that is truly a duplicate then maybe you have a
more underlying problem. You will always get a CPF2450 when trying to
allocate a workstation message queue to a job different than the job with
it's device. Message queue MYWSID can only be associated with the job
jobNumber/jobUser/MYWSID. The help kind of says that. Instead of trying
to compute &WSID, why don't you just use the generic?
CHGMSGQ MSGQ(*WRKSTN) DLVRY(*BREAK)
The very rare case you may get this to work will be when there's a device
named the same as the user.
Object Type Library Text
ROB *MSGQ QSYS Work Station Message Queue
ROB *MSGQ QUSRSYS Rob Berendt - GDI - Systems
You 'think' you're getting the workstation message queue(QSYS), but you're
actually getting the message queue for the user(QUSRSYS).
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail
to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
From: "Steinmetz, Paul" <PSteinmetz@xxxxxxxxxx>
To: "'Midrange Systems Technical Discussion'"
<midrange-l@xxxxxxxxxxxx>
Date: 07/27/2015 11:45 AM
Subject: Strange seesion issue - message q issue
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
I had a strange session issue on 2 of 6 sessions for user.
I think the problem was something with the mssq associated with each of
these two sessions.
I was able to recreate the issue pointing my session to of the two
sessions.
In our initial program to call, we set the session message q to break.
CHGMSGQ MSGQ(&WSID) DLVRY(*BREAK)
Message . . . . : 509 - CHGMSGQ
MSGQ(PALPR5641F) DLVRY(*BREAK)
CPF2450 Escape 40 07/27/15 08:07:45.016597 QMHCHMSQ
QSYS 0994 SIGNONCLEX BRCPGMS 0030
Message . . . . : Work station
message queue PALPR5641F not allocated to
job.
CPA0701 Inquiry 99 07/27/15 08:07:45.017726 QCLXERR
QSYS 00C6 *EXT *N
Message . . . . : CPF2450 received
by SIGNONCLEX at 509. (C D I R)
I renamed the two corrupt sessions to a different name, (which also
renamed the msgq).
The problem is now gone.
Any ideas on what can happen to a message q that causes corruption?
Thank You
_____
Paul Steinmetz
IBM i Systems Administrator
Pencor Services, Inc.
462 Delaware Ave
Palmerton Pa 18071
610-826-9117 work
610-826-9188 fax
610-349-0913 cell
610-377-6012 home
psteinmetz@xxxxxxxxxx
http://www.pencor.com/
midrange.com
