Re: An Interesting One

[dslessman@xxxxxxxxxxxxxxxxxxxxxx]

Sounds like the job is cleaning up is "temporary" working areas (ie, qtemp,
job log, etc) and that is what is taking so long.  Check the job when it is
running and see if it is set to LOGCLPGM(*YES) or something like LOG(4 00
*SECLVL).  Hope that helps.




                                                                                
                                     
                    tbutala@dentspl                                             
                                     
                    y.com                  To:     BPCS-L@midrange.com          
                                     
                    Sent by:               cc:                                  
                                     
                    owner-bpcs-l@mi        Subject:     An Interesting One      
                                     
                    drange.com                                                  
                                     
                                                                                
                                     
                                                                                
                                     
                    03/30/2000                                                  
                                     
                    03:28 PM                                                    
                                     
                    Please respond                                              
                                     
                    to BPCS-L                                                   
                                     
                                                                                
                                     
                                                                                
                                     





I have an interesting one happening right now.  We have three AS/400s, two
of
them identical.  We run BPCS 6.0.04.  We just upgraded our operating system
to
V4R4.  On the one AS/400 our batch allocation program ORD400B completes
processing but does not close down for a long period of time.  That's
right, all
BPCS jobs will clear through the job stack, the status of the job goes to
END
but it sits in the END status for an hour or more before it finally closes
on
its' own.

Personally I have never seen a job do this before, I've seen the hang where
I
had to cancel them, but this job will eventually close out on its' own.
Because
this problem started once the new release was applied this weekend my
assumptions (yes I know about assumptions) is that this is an Operating
System
problem.  However, this problem does not occur on either of the other
AS/400s.
We have contacted IBM and they have had us load a number of new PTF's and
wanted
us to run DBMON over the process to create new access paths (which we did)
all
to no avail.  SSA does not have any answers for us either.

My question is simply, has anybody else had a similar problem and if so
what
resolved the issue.


+---
| This is the BPCS Users Mailing List!
| To submit a new message, send your mail to BPCS-L@midrange.com.
| To subscribe to this list send email to BPCS-L-SUB@midrange.com.
| To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: dasmussen@aol.com
+---




+---
| This is the BPCS Users Mailing List!
| To submit a new message, send your mail to BPCS-L@midrange.com.
| To subscribe to this list send email to BPCS-L-SUB@midrange.com.
| To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: dasmussen@aol.com
+---