Re: Prestart Jobs

--




Bill,

QZLSFILE is actually a subsystem prestart job for AS/400 NetServer (file share)
running in subsystem QSERVER.
--

 There is one active  QZLSFILE  job for each
active client (PC user). QUSER isn't useful because it is just the servicing
profile for the prestart job. Instead you need to fine the client requesting
user. To attempt this you could try the following :

1. Next time the job runs and goes to message wait try  using Operations
Navigator go Work Management, go Server Jobs. Find QZLSFILE jobs and get
properties to see which user is running in the job and the IP address of the
client.

2. If job not running try WRKJOB JOB(QPRTJOB). This displays a list of prestart
jobs requesting users that have produced spooled output. Zoom into this and you
get a list of their jobs. Hopefully, the failed job will have produced output
because it was cancelled. Match up dates and times with users and you should
catch the culprit.

Good luck,

Keith
|+-------------------+------------------------------------|
||   "bill totz"     |                                    |
||   <robsurge@hotmai|           To:                      |
||   l.com>          |   RPG400-L@midrange.com            |
||                   |           cc:        (bcc: Keith   |
||   06/09/02 20:37  |   McCully/Wunderman/GB)            |
||   Please respond  |           Subject:        Prestart |
||   to rpg400-l     |   Jobs                             |
||                   |                                    |
|+-------------------+------------------------------------|






[IMAGE]

Has anyone had an issue with Prestart Jobs? I keep getting this job running
in Subsystem:QZLSFILE User: Quser as noted below:

  Message ID . . . . . . :   CPA3138
Date sent  . . . . . . :   09/04/02      Time sent  . . . . . . :   04:57:56

Message . . . . :   Member BUSX file BUSX at maximum size. (C I)

Cause . . . . . :   A request was made to add records to member BUSX file
BUSX
  in library AD.LIB that is greater than the number of allowed file
  increments. If the operation being preformed is an Initialize Physical
File
  Member (INZPFM) operation, then this message is sent only for the first
of
  these increments that are required. The file will be extended to the
  requested size and this message will not be signaled again, even if
  additional increments are required. Otherwise, if the operation being
  performed is not an Initialize Physical File Member operation then this
  message is sent each time a new file increment is required.
Recovery  . . . :   Do one of the following:

More...
Type reply below, then press Enter.
Reply  . . . .

F1=Help   F3=Exit   F6=Print      F9=Display message details
F10=Display messages in job log   F12=Cancel   F21=Select assistance level


This is the only reason we found the job. This program seems to run through
every object on our system and at times will add hundreds of blank records
to files and tables which in turn halts and crashes pgms. I have spoken to
our IBM service rep but he doesn't seem to have clue(and is also on vacation
this week and next week). Is it possible that our 400 has a virus? We
recently cleaned up a klez worm approximately 6 weeks ago. I'm really
stumped on this one!!!

Thanks









_________________________________________________________________
Chat with friends online, try MSN Messenger: http://messenger.msn.com

_______________________________________________
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l
or email: RPG400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.


(Embedded image moved to file: pic28952.pcx)
--
[ pic28952.pcx of type application/octet-stream deleted ]
--