|
I am going to submit a DCR that IBM add an OBJAUD option to CRTDEVPRT. The
default option should be *LIB so that it can use the setting from
CHGLIB QSYS CRTOBJAUD(...)
However, IBM should allow us to change this with
CHGCMDDFT CMD(CRTDEVPRT) NEWDFT('OBJAUD(*CHANGE)')
Because I may not want object auditing on all objects within QSYS. One of
the daily things I am finding I must do is:
ENDWTR newprinter
CHGOBJAUD newprinter OBJTYPE(*DEVD) OBJAUD(*CHANGE)
and restart the writer.
Mimix has an option to try to change the object auditing value but it
won't stop the writer. And that has to be done before you can CHGOBJAUD.
I feel their pain. Restarting a writer, when it can be local, remote,
InfoPrint server, etc and getting all the options right, can be a pain. We
wrote our own RSTWTR to determine what the proper start of the writer
should be.
Therefore getting the object auditing right in the first place is the way
to go.
Any Mimix aficionados out there want to submit a like DCR and help push
this change through?
Or how else do you handle it?
https://www-912.ibm.com/r_dir/ReqDesChange.nsf/Request_for_Design_Change?OpenForm
====================================================
Detailed description of the request (including unique usage)*
====================================================
Mimix shop. Mimix uses object auditing to help duplicate objects.
However, when I create a printer device it defaults it to *NONE. It does
this because the new object only gets this value from:
WRKSYSVAL QCRTOBJAUT
and
CHGLIB ... CRTOBJAUD.
I don't want to start object auditing on everything in library QSYS, nor
do I want to start object auditing on everything in the whole system.
Therefore I need more granularity.
One of the daily things I am finding I must do is:
ENDWTR newprinter
CHGOBJAUD newprinter OBJTYPE(*DEVD) OBJAUD(*CHANGE)
and restart the writer.
Mimix has an option to try to change the object auditing value but it
won't stop the writer. And that has to be done before you can CHGOBJAUD.
I feel their pain. Restarting a writer, when it can be local, remote,
InfoPrint server, etc and getting all the options right, can be a pain. We
wrote our own RSTWTR to determine what the proper start of the writer
should be.
Therefore getting the object auditing right in the first place is the way
to go.
====================================================
Solution suggestions (include your ideas for a solution)
====================================================
Add an OBJAUD option to CRTDEVPRT. The default option should be *LIB so
that it can use the setting from
CHGLIB QSYS CRTOBJAUD(...)
However, IBM should allow us to change this with
CHGCMDDFT CMD(CRTDEVPRT) NEWDFT('OBJAUD(*CHANGE)')
Because I may not want object auditing on all objects within QSYS.
I can see other commands needing this option added in the future.
Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
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.