Could be any number of things.  For example, on an unrelated object, if I 
do
DSPOBJD OBJ(QCMDEXC) OBJTYPE(*PGM) DETAIL(*SERVICE)
I'll see:
PTF number . . . . . . . . . . . . . :   SI15146

Now, if you knew the affected object(s) by this new ptf, you could do the 
same.  Then on the affected machine do the DSPOBJD thingy and see if you 
have a ptf on it.  See if the working machines have the same, a different 
ptf, or no ptf on it.

In summary, you may be at different ptf levels on the machines.  One ptf 
may be in error and causing you grief.  Or, it may be a ptf that causes 
things to work the way you are and some people may have wanted it that 
way.  Just like the ptf to change DSPJOB OPTION(*OPNF) to not default to 
showing you the activation group first.  A ptf that will never make it to 
a cume.

Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2025 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.