Journaled Job Logs

[Guest.Visitor]

I recently moved from an E35 to a Model 170 and have encountered som job logs that I do not understand. The job name is: QZSCSRVS with Job description: QZBSJOBD, user: QUSER. A job log is constantly being produced for CPF1301 Severity 30 - message : ACGDTA for 99999/QUSER/QSCSRVS not journaled; reason 1. Per the cause this is being created due to the system value QACGJRN indicates this accounting level of resource was not meant to be done when the job entered the system. The error and cause appear to be in conflict - the system value says not to journal but the log is created. How do I get rid of this job log without harming other messages I may need regarding this job? I must get over 30 of these each day. My old system did not create this log and I need a better understanding of why. Any help is greatly appreciated in advance. Randy K. Lessor rlessor@pizzagalli.com

[Guest.Visitor]

On Thursday, April 01, 1999, 08:55 AM, Randy K. Lessor wrote: I recently moved from an E35 to a Model 170 and have encountered some job logs that I do not understand. The job name is: QZSCSRVS with Job description: QZBSJOBD, user: QUSER. A job log is constantly being produced for CPF1301 Severity 30 - message : ACGDTA for 99999/QUSER/QSCSRVS not journaled; reason 1. Per the cause this is being created due to the system value QACGJRN indicates this accounting level of resource was not meant to be done when the job entered the system. The error and cause appear to be in conflict - the system value says not to journal but the log is created. How do I get rid of this job log without harming other messages I may need regarding this job? I must get over 30 of these each day. My old system did not create this log and I need a better understanding of why. Any help is greatly appreciated in advance. I think the error and the production of the joblog may be unrelated. You did not give a release... but I will infer you are on V4R3M0, so you will want SF53888 to prevent the joblog; a correction to condition where a joblog is being produced even though the logging level is LOG(4 0 *NOLIST). DSPJOBD QSYS/QZBSJOBD will likely show that. The other condition is a result of work management, during a request to 'switch user' to the serviced profile. When there is no ACGCDE defined in the user being switched-to, the error is logged. Because some other server jobs in the past had removed the message, the Work Management dev decided not to make a generic fix -- best I can infer anyway; relying on each requestor of the switch user function to decide whether to remove the message from the joblog if desired. The component responsible for the jobs you note, has claimed they may change to remove the message in a future release... but they did not give this via an official response in APAR SA77381. Of course then, to rid of that specific message, you could just give your user profiles accounting codes. BTW you can find the APAR I found by visiting target=_new href="http://as400service.rochester.ibm.com/supporthome.nsf/home/Software+Proble ms+-+APARS"> href="http://as400service.rochester.ibm.com/supporthome.nsf/home/Software+Proble ms+-+APARS">http://as400service.rochester.ibm.co.../home/Software +Problems+-+APARS which is found via the Technical info & Databases and Software problems - APARs from href="http://as400service.rochester.ibm.com"> href="http://as400service.rochester.ibm.com">http://as400service.rochester.ibm. com A search to use would be the token: MSGCPF1301 Regards, Chuck Comments provided "as is" with no warranties of any kind whatsoever.

[Guest.Visitor]

Chuck, thanks for your help. I have gone to get the PTF SF53888 and will apply this weekend. keeping my fingers crossed. Randy K. Lessor

[Guest.Visitor]

Chuck, thanks for your help. I have gone to get the PTF SF53888 and will apply this weekend. Keeping my fingers crossed. Randy K. Lessor