RE: Browsing a spool file from within a source member acts differentl y

Bob,

No. The spool number still shows last.  It's as if the system has lost track
of the job number parm and just uses the job name and user.

Vern,

These are batch compiles.  Sorry, I should have included that in the first
message.  I haven't knowingly changed the SEU settings recently.  We are at
V5R2.  I don't know the cume number.  Operations tell me it is the latest
one but I can't display PTF information to get a number.

Rick

-----Original Message-----
From: Vern Hamberg [mailto:vhamberg@xxxxxxxxxxxxxxxxxxxxxxxxx]
Sent: Monday, March 03, 2003 2:50 PM
To: Midrange Systems Technical Discussion
Subject: Re: Browsing a spool file from within a source member acts
differentl y

Rick, is this the message where you need to use F4 in the spooled file name
field?

Are these batch or interactive compiles? Have you changed your SEU settings
(F18)?

What VRM? CUME level?

At 01:44 PM 3/3/2003 -0600, you wrote:
>Has anyone else encountered a change in behavior when using F15 to include
a
>spool file from within a source member?  Until last week when I edit a
>source member and want to view compile errors I would simply press F15 and
>change the selection to spool file (2) to display the latest compile
listing
>in the lower half of the screen.  Now when I do this I receive a message
>that duplicate jobs are found and must prompt and then select the spool
file
>I want to view.  I think our operations group applied PTF's that caused
this
>change but they tell me they can't find any information about this in PTF
>cover letters and APAR's.
>
>Any ideas?
>
>Rick Chevalier
>Sr. Programmer Analyst
>
>(817) 525-7178
>rick.chevalier@xxxxxxxxxxxxxxx


_______________________________________________
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.