RE: INV900 Oops

When we run monthend, we have set up a cl that does an endsbs on qinter and
batch subsystems where BPCS related jobs may process.  We also do an endpj
qusrwrk/qzdasoint *immed, which takes care of the ODBC jobs.

D. Eddy

-----Original Message-----
From: Clare Holtham [mailto:Clare.Holtham@xxxxxxxxxxxxxx]
Sent: Thursday, June 05, 2003 11:55 AM
To: SSA's BPCS ERP System
Subject: Re: INV900 Oops


What about TCP/IP and ODBC connections??

Clare

Clare Holtham
Director, Small Blue Ltd - Archiving for BPCS
Web: www.smallblue.co.uk
IBM Certified AS/400 Systems Professional
E-Mail: Clare.Holtham@xxxxxxxxxxxxxx
Mobile: +44 (0)7960 665958
----- Original Message -----
From: "Bielskus, Mindaugas" <Mindaugas@xxxxxxxxx>
To: "SSA's BPCS ERP System" <bpcs-l@xxxxxxxxxxxx>
Sent: Thursday, June 05, 2003 4:25 PM
Subject: RE: INV900 Oops


> At this client, we automatically run INV900 as part of the month-end batch
> program that just calls various BPCS programs.  To insure that nobody has
> access to the system, all the workstations are varied off and nobody can
get
> past the main BPCS menu, if they did sign-on with the system automatically
> creating device descriptions.  Once the month-end program reaches a point
> where it is safe to let users sign back on, all the device descriptions
are
> varied back on and then sign-on to BPCS enabled.
>
> We have been doing this for about five years, for every month-end.
>
> In general, I would say that if you know what the parameters for a
> particular program need to be, set-up for multiple runs should be done
once
> per year when you have your full attention devoted to that task.  Why do
> through all that stress every month-end?
>
> Mindaugas Bielskus
>
> -----Original Message-----
> From: Al Mac [mailto:macwheel99@xxxxxxxxxxx]
> Sent: Wednesday, June 04, 2003 1:05 PM
> To: SSA's BPCS ERP System
> Subject: RE: INV900 Oops
>
>
> Hopefully our latest scenario has been resolved.  Thanks to all who made
> some suggestions.
> I discussed Dee Dee's post with my boss, and last nite after an early
> backup I ran INV900.
>
> During INV900 we periodically use QSECOFR or QSYSOPR to check on if it is
> done yet, because we know from experience that a person can sign on, just
> be at a menu, but now there is a lock blocking INV900 from
> continuing.  Even the work station that launched INV900 can cause this, by
> moving around to other menus.
>
> Before INV900 we vary off 100% of the work stations accessible to nite
> shift.
> They are accustomed to accessing BPCS when they want to check on
inventory,
> BOM, shop orders, whatever ... they not really understand various reasons
> why stay off at this or that time, and there are a lot of individual
> inspectors, team leaders, etc, who might randomly need to use one of the
> factory work stations.
>
> When INV900 done, I vary their work stations back on again.
>
> INV900 is usually run by an accounting person who not fully understand
that
> not all jobs are shown on WRKACTJOB ... there may be stuff that is
> DISCONTINUED but still tying up BPCS files ... and of course there is
stuff
> on JOBQ other than what YOU put there.
>
> I have discovered with reorgs like SYS120 that it can run with other
people
> on the system.
> It pauses with a lock on this or that file, then skips that file and moves
> on to the next file.
> So basically I can do a reorg which does the files they not happen to be
> using at the moment, without kicking them off of BPCS like we have to do
> with INV900.
>
> Al Mac
>
> >I frequently have issues with INV900 not running. More accurately, it
> >says "Ended abnormally." When I DSPMSG. It's always because a user had
> >the IIM file open and INV900 could not get the exclusive lock it needs.
> >Sometimes the user is not in, but the IIM file stays locked because they
> >did not sign off before closing the session window. In that case, I do a
> >wrkobjlck on the IIM file and determine the job(s) that are locking the
> >file. I then take action 4 to end the job.
> >
> >Hope this helps!
> >
> >Paul
> >
> >
> >
> >-----Original Message-----
> >From:  DeeDee Virgei
> >
> >Hi,
> >
> >We are on 4.05 CD...  When we run inventory M/E (INV900), INV901C then
> >gets
> >submitted to batch...  Since your INV901C program wasn't used this month
> >and
> >from the last dates used on your other programs, it looks like during
> >submission of your M/E,  the options on the 2nd of screen of INV900 were
> >set
> >as follows:
> >INV900-02 ...
> >           Print all Outstanding Cycle Counts        Y      (Y or N)
> >
> >           Continue with Month End Procedure      N      (Y or N)
> >
> >
> >These are the defaults setting; we have to change them every month to N
> >then
> >Y...  This being the case, the impact would be pretty much the same as
> >not
> >running INV900 at all.  We once forgot to run INV900; ended up running
> >it
> >the next evening and had to make some adjustments to some of the
> >reports...
> >
> >Hope this helps.
> >
> >
> >DeeDee Virgei
> >Nelson Stud Welding, Inc.
> >7900 West Ridge Rd
> >Elyria, OH 44036
> >
> >  -----Original Message-----
> >From:   Al Mac
> >
> >I am looking for suggestions while I struggle looking into some things.
> >We are BPCS 405 CD
>
> <snip>
>
> >___
>
> Al Macintyre
>
> _______________________________________________
> This is the SSA's BPCS ERP System (BPCS-L) mailing list
> To post a message email: BPCS-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/bpcs-l
> or email: BPCS-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/bpcs-l.
>
>
> ________________________________________________________________________
> This e-mail has been scanned for all viruses by Star Internet. The
> service is powered by MessageLabs. For more information on a proactive
> anti-virus service working around the clock, around the globe, visit:
> http://www.star.net.uk
> ________________________________________________________________________
>
> DISCLAIMER: This e-mail transmission is strictly confidential. If you are
> not the intended recipient, you must not copy, distribute or take any
action
> in reliance on it. If you have received this e-mail in error, please
notify
> us as soon as possible and delete it.
> E-mail transmission cannot be guaranteed free from viruses, secure or
error
> free. No liability is accepted by the sender for any loss or damage which
> may be caused as a result of the transmission of this e-mail. If
> verification is required, please ask for a hard copy version.
>
>
> _______________________________________________
> This is the SSA's BPCS ERP System (BPCS-L) mailing list
> To post a message email: BPCS-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/bpcs-l
> or email: BPCS-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/bpcs-l.
>
>

_______________________________________________
This is the SSA's BPCS ERP System (BPCS-L) mailing list
To post a message email: BPCS-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/bpcs-l
or email: BPCS-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/bpcs-l.