SV: SBMJOB LOGCLPGM(*NO) and CPI2417 -- MIDRANGE-L

Ver,

The LOG paramter is set to 0 00 *NOLIST.
But still there are still a msg in qsysopr.

Here is the joblogg with logging on from the jobb.


   05-03-01  15.42.20,646408  QCLCLCPR     QSYS        045C     FLDI009    
MSG  . . :     2400 - CALL PGM(SACTDP1)          /* The CALL command
  contains parameters */                                                   
   05-03-01  15.42.20,654936  QCLRTNE      QSYS        0058     FLDI009    
MSG  . . :          - RETURN        /* RETURN due to end of CL progr
  */                                                                       
   05-03-01  15.42.20,656280  QCLCLCPR     QSYS        045C     FLDI009    
MSG  . . :     2400 - CALL PGM(SACTDP1)          /* The CALL command
  contains parameters */                                                   
   05-03-01  15.42.20,665064  QCLRTNE      QSYS        0058     FLDI009    
MSG  . . :          - RETURN        /* RETURN due to end of CL progr
  */                                                                       
   05-03-01  15.42.20,665232  QCLCLCPR     QSYS        045C     FLDI009    
MSG  . . :     2400 - CALL PGM(SACTDP1)          /* The CALL command
  contains parameters */                                                   
   05-03-01  15.42.20,673672  QCLRTNE      QSYS        0058     FLDI009     


Regards
Jan Rockstedt


-----Ursprungligt meddelande-----
Från: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] 
För Vernon Hamberg
Skickat: den 2 mars 2005 13:19
Till: Midrange Systems Technical Discussion
Ämne: Re: SBMJOB LOGCLPGM(*NO) and CPI2417

Jan

What is the LOG parameter setting? The help for this says

Message logging (LOG) - Help
Specifies the message logging values used to determine the amount and type of 
information sent to the job log by this job.

If you have anything other than 0 for the first element of the JOB parameter, 
things are being written to the jobs message queue, which is where the job log 
comes from. And this happens whether you see s job log or not. That could be 
because the 3rd element is *NOLIST, which does NOT mean 'don't put any messages 
in the job <SGQ'. It means, as the help says, print a log only if the job ends 
in error - messages are still being written, in case a job ends abnormally. 
Look at the rest of the help on that parameter. 
You can eliminate logging completely but will get no error indicators other 
than probably in QSYSOPR. You'll want to use something other than 0 with a 
severity level of, say, 20 or 30, so that warnings and errors come through. 
Or maybe higher.

The question I have is, what in the world is causing all the messages in the 
first place?

HTH
Vern

At 02:19 AM 3/2/2005, you wrote:
>Hi!
>
>We have problem with a submited job.
>The job is runing with SBMJOB LOGCLPGM(*NO), and there are no joblog if 
>i work with the jobb.
>
>But still we get in qsysopr msgq CPI2417 that the job has CPI2417 - job 
>message queue wrapped.
>Yes the sysval QJOBMSGQFL is set to *WRAP.
>
>Ho do i get rid of the CPI2417 i qsysopr?
>
>Regards Jan Rockstedt
>
>--
>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.

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