• Subject: CA/400 Prestart job ending by itself (QNPSERVR)
  • From: "Roger Vicker, CCP" <rvicker@xxxxxxxxxx>
  • Date: Fri, 28 Jan 2000 16:10:32 -0600
  • Organization: Vicker Programming Systems

Hi,

I've got a customer with a model 620 running V4R2M0 that is being accessed by twinax PCs using CA/400 V3R2M0 (current SP) but the network print job in QCMN (QNPSERVR) keeps ending. I found a note on IBM that a few PTFs were required and applied them. Otherwise I haven't been able to find anything (RTFM or Midrange-L archives) that explains this. I can STRPJ QCMN QIWS/QNPSERVR and everyone can use the AS/400 as a print server for a while but eventually the the job(s) end. After that any PC that tries to access the AS/400 network printer generates a QSYSOPER message:

Message ID . . . . . . :   CPF1269       Severity . . . . . . . :   00
Message type . . . . . :   Information
Date sent  . . . . . . :   01/24/00      Time sent  . . . . . . :   15:16:04

Message . . . . :   Program start request received on communications device
  FWDPC316 was rejected with reason codes 804, 0.
Cause . . . . . :   The program start request was rejected in job
  126979/QSYS/QCMN. The device belongs to remote location FWDPC316. If the
  device is an advanced program-to-program communications (APPC) device, the
  program start request was received on mode QPCSUPP with unit-of-work
  identifier APPN.S102M5DM-404040404040-0001. The first reason code means:
  Prestart job is inactive or is ending. The second reason code means: None.
Recovery  . . . :   See the job log for more information about the problem.

The joblog for QCMN shows a message of :

Message ID . . . . . . :   CPF1283       Severity . . . . . . . :   60
Message type . . . . . :   Completion
Date sent  . . . . . . :   01/28/00      Time sent  . . . . . . :   15:02:49
 
Message . . . . :   Subsystem QCMN cannot start prestart job QNPSERVR.
Cause . . . . . :   Prestart job 146091/QUSER/QNPSERVR that uses program
  QNPSERVR in library QIWS cannot be started because an error in the program
  occurred before the device was acquired.
Recovery  . . . :   Display the job log for the job for more information. Wait
  until message CPC0905 appears on the QSYSOPR message queue, indicating that
  the entry is no longer active. To start new jobs, enter the Start Prestart
  Jobs (STRPJ) command.

Before (sometimes after) that there is usually but not always a message:

Message ID . . . . . . :   CPF0920       Severity . . . . . . . :   60
Message type . . . . . :   Completion
Date sent  . . . . . . :   01/28/00      Time sent  . . . . . . :   14:45:05
 
Message . . . . :   All prestart jobs are ending for program QNPSERVR in QIWS.
Cause . . . . . :   All prestart jobs for program QNPSERVR in library QIWS in
  subsystem QCMN are ending for reason 2.  See reason 2 shown below:
    1 - The End Prestart Job (ENDPJ) command was entered.
    2 - An error occurred when new jobs were being started.
    For reason 2, display the job log (DSPJOBLOG command) for the subsystem to
  determine the cause of the error.
    When all the prestart jobs have ended, message CPC0905 will appear in the
  subsystem job log and the system operator message queue.
Recovery  . . . :   To start jobs, display the system operator (QSYSOPR)
  message queue (DSPMSG command). After message CPC0905 appears in the message
  queue, enter the Start Prestart Jobs (STRPJ) command.

Any advice before I go to Support Line? Since the system is 400 miles away from the PCs the co-ordination can be complicated.

TIA

Roger Vicker, CCP

--
*** Vicker Programming and Service *** Have bits will byte *** www.vicker.com ***
If it ain't broke, always try to fix it anyway.
 


As an Amazon Associate we earn from qualifying purchases.

This thread ...


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

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