Re: iSeries Access and *break job completion messages?

Hi Tony

Does the initial program set the workstation msgq to break ? (I don't
suppose there was a startup macro or sequence defined in the old set up
that did this was there ?)

It seems to me that this is more likely to have something to do with the
initial signon particularly if the delivery mode is changed; i understand
that to be a job setting as opposed to a device setting.

The user profile message queue would be meaningless if the message is being
sent to a workstation message queue wouldn't it ? I'd expect to see
CHGMSSGQ MSGQ(*WRKSTN) DLVRY(*BREAK) or something like it in the signon
program if the messages are being sent to the workstation queue. This seems
likely to not have worked anyway without something in the initial program.

If you set your session up the same and it works then reconsider the human
factor. I have encountered situations where users have noticed a problem
"caused by something new" that was actually there all along.

It would be well worth checking what happens with one user and then
upgrading them to get more of a handle on what changes, including watching
them start, signon, get the message and sign off both before and after.

They arent signing off and getting the messages while signed off are they ?

Hope this helps at least a little bit.

Help!!

Here's the situation:
We just installed V4R5 and will be putting on 5.2 in January.  The client
access config on the user's desktops is set up so that they have one icon on
the desktop and the sessions are named QPADEV####.  The user profile is set
up with MSGQ(username) LIBRARY(QUSRSYS) and DLVRY(*BREAK).

In other words, they're using unnamed CA sessions and they get a break
message on completion of a submitted job.

We are installing iSeries Access V5R2 (from an image with the latest service
pack rolled in) and the users we've upgraded so far are NOT getting the
break messages, they're going to the MSGQ named after the session in *NOTIFY
mode.  I set up my session config the same, and it works OK.  The only
differences I can see are that I'm on Win2K, the users are on W98, and they
have a "typical" install, I have everything, I installed from the CD and
added the service pack, users are installed from the "SP rolled in" image.
The CA configuration panel shows "Specify Workstation ID" = *blank, "Add
Prefix" and "Avoid Duplicate Names..." checkboxes are blank, and "Bypass
Signon" is checked (even though it doesn't).

To restate this problem in few words: the users are not getting *break
messages at the completion of a job now, but they did on CA V3R2.

I do not get it.

I've spoken to the Supportline folks and so far, they haven't "got it"
either.  I'll call back tomorrow when I can sit beside a user with a
problem.

Any help will really be appreciated.

AS/Resources, Inc.
William A.(Tony) Corbett
IBM Certified Specialist - AS/400 Developer
http://www.asresources.com
corbett@asresources.com
770-587-4812 (office)
678-935-5006 (mobile)
fax:  404-663-4737




_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.