being forced to use the activation group on WRKJOB/DSPJOB.

["Simon Coulter" <shc@xxxxxxxxxxxxxxxxx>]

Hello Rob,

You wrote:
>Re: being forced to use the activation group on WRKJOB/DSPJOB.

>This recently brought to light a problem here.  They had the file opened in
>the wrong activation group and it showed in this screen.

That information would still show up but you'ld need to press F11 to see it.  
I'm not saying the activation group information is compeletely useless, just 
that it is not the most useful information on that display.  I maintain that 
the I/O information is of much more use than the activation group 
information and that statement is supported by the number of requests on 
this list for the PTFs that 'correct' the behaviour when a new release is 
installed!

Given that the PTFs in question never make it on to a Cume it would be 
interesting to know how many people have actually downloaded them.

>How many people would think it was great if the first thing that option 14
>to compile a RPG/400 program did was convert it to RPG/IV over top of the
>RPG/400 source and then compile it?  Me, for one.  And if you didn't want
>this then you could order a PTF.

This analogy is flawed -- comparing Apples and Oranges.  You are 
comparing a suggestion for making serious changes to existing code to a 
trivial change that shows relatively useless information at the expense of 
extremely useful information.  

You may indeed desire that behaviour but the correct approach in this case is 
to give YOU a PTF to apply to change the 
default/expected/backwards-compatible behaviour.  Not force the rest of us to 
apply a PTF to get things back the way they belong!

The correct approach to adding the activation group information to the 
WRKJOB/DSPJOB panels waaaaaay back in V2R3 was to add a new function key 
(F11=Display scoping data/F11=Display I/O details) to toggle the panel 
between the two displays but cause the existing data to remain on the first 
screen by adding the new view after the existing view. The panel is using UIM 
and the problem is due to the order of the :LISTVIEW tags being transposed.  
The PTF however probably adds code to the driving program to set the initial 
view to 1 instead of the default of 0 to avoid PTFing MRI.

Regards,
Simon Coulter.

«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»
«» FlyByNight Software         AS/400 Technical Specialists       «»
«» Eclipse the competition - run your business on an IBM AS/400.  «»
«»                                                                «»
«» Phone: +61 3 9419 0175      Mobile: +61 0411 091 400           «»
«» Fax:   +61 3 9419 0175      mailto: shc@flybynight.com.au      «»
«»                                                                «»
«» Windoze should not be open at Warp speed.                      «»
«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@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
+---