|
midrange.com
Sorry to jump in - I'm sure Jeff will answer with details of the task
numbers for inventory and manufacturing, but I wanted to mention the G/L
subsystem. There is a flag on a data area (pos 11 in GLSBSDTA) that is
used to ensure the G/L background job is not running when certain rebuilds
are being run (e.g. G/L Hierarchies).
Basically the job wakes up from sleep and immediately checks this flag. If
it is set on (say a rebuild is running), the system goes back to sleep. If
the flag is not set on then the flag is set on and then the job looks for
journals awaiting update. If it can't find any for update, (or when it
has finished updating), the flag is set off and the job goes in sleep
mode.
It is possible that with an ENDSBS that the job ends during one of these
checks, leaving the flag set on. When you start the subsystem again, the
job goes active and appears to be working - sleeping, waking, running,
sleeping - but all it is doing is checking the flag and going back to
sleep. I have known this to happen for several days before someone
realized that the G/L was not being updated.
Tasks GL 03 0001 and GL 03 0002 should be used to start and end the
subsystems.
Richard
"Gaffney Mitchell, Theresa" <Theresa.Gaffney@xxxxxxxxxx>
Sent by: system21-bounces@xxxxxxxxxxxx
11/05/2003 07:58 AM
Please respond to System 21 Users
To: system21@xxxxxxxxxxxx
cc:
Subject: RE: [SYSTEM21] Save while Active
Jeff,
How are you ended your subsystems? On some of my system 21 subsystems I am
just doing an "ENDSBS *immed". But ones like inventory and manufacturing
would not go down clean if I did that.
Any suggestions?
Thanks,
Theresa
-----Original Message-----
From: Jeff Klipa [SMTP:jklipa@xxxxxxxxxxx]
Sent: Wednesday, November 05, 2003 8:51 AM
To: system21@xxxxxxxxxxxx
Subject: Re: [SYSTEM21] Save while Active
Jon,
We have automated our nightly routine to terminate the
JBA
subsystems and
End SBS QINTER in order to do 4 things...
1.) Run the AM Day End job.
2.) Run the CF Day End job.
3.) Clear bogus active record locks and run CLNUSRALC to
free up
bogus seat
allocations.
4.) Initiate the SAVLIB *ALLUSR job.
Both 1 and 2 require that no users be signed into JBA or
else they
will hang
and the night job will also hang. That's not a good
thing... We
have set
our Inactivity timer to 120 minutes so if a user leaves
him/herself
signed
on when they go home the system will terminate their
interactive
session.
There are 3 options for the Save While Active parameter
that you
need to
choose from...
*LIB
Objects in a library can be saved while they are in
use by another job. All of the objects in a library
reach a checkpoint together and are saved in a
consistent state in relationship to each other.
Note: Libraries with thousands of objects may be
too large for this option.
*SYNCLIB
Objects in a library can be saved while they are in
use by another job. All of the objects and all of
the
libraries in the save operation reach a checkpoint
together and are saved in a consistent state in
relationship to each other.
Note: If you specify this value and you are
saving many libraries, it can take a long time to
reach a checkpoint for all of the objects and
libraries in the save operation.
*SYSDFN
Objects in a library can be saved while they are in
use by another job. Objects in a library may reach
checkpoints at different times and may not be in a
consistent state in relationship to each other.
Note: Specifying this value eliminates some
size
restrictions and may enable a library to be
saved
that could not be saved with SAVACT(*LIB).
>From a disaster recovery standpoint I doubt that *SYSDFN
would be a
good
choice.
And *LIB probably would not work due to the large number
of objects
in the
file library...
So, *SYSDFN may be the best of the 3 options... But you
are the
only person
who can decide what's best for your situation.
>From my perspective you must have a small slice of time
where the
users are
not locking the JBA library list file APG25PHY so that
you can run
the
AMDAYEND and CFDAYEND jobs at a minimum... Having that
window of
opportunity to initiate the SAVLIB command would also
seem to make
sense
from the standpoing of establishing a checkpoint. If
only to
shutdown and
restart the background subsystem jobs. There used to be
a problem
with the
job date not rolling forward at midnight, but I don't
know if that's
still a
problem.
Our users are offline for approximately 1/2 hour. Our
save starts
around
1:30 AM and runs for about 8 or 9 hours. We use BRMS
with a 3570
MAGSTAR
and our backup uses 4 tapes. We run a 720.
I say tell them you need a 15 minute window and schedule
it for the
time of
day when there is the least demand on your system...
I know there will probably be lots of input on this
topic... Should
prove
interesting... I welcome opposing viewpoints...
Good luck...
----Original Message Follows----
From: JonWadey@xxxxxxxxxxxxx
I've been asked by our new parent company, for 24 hrs
operations on
one
box. With this in mind the only way I can think of doing
a nightly
save
is via the save while active command. Does anybody out
there use
this
method of saving and if so what problems if any have they
come
across?
I am aware that any active objects will not be saved at
the time and
this
could lead to data being saved at different times.
TIA
Jon
Jon Wadey
IT Manager
M & S Toiletries Ltd
Tel :- (+44) 1506 835600
Fax :- (+44) 1506 835609
_________________________________________________________________
MSN Messenger with backgrounds, emoticons and more.
http://www.msnmessenger-download.com/tracking/cdp_customize
_______________________________________________
This is the System 21 Users (SYSTEM21) mailing list
To post a message email: SYSTEM21@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/system21
or email: SYSTEM21-request@xxxxxxxxxxxx
Before posting, please take a moment to review the
archives
at http://archive.midrange.com/system21.
_________________________________________________________________
This electronic mail transmission contains confidential information
intended
only for the person(s) and/or organization named. Any use, distribution,
copying or disclosure by or to any other person outside your organization
is
strictly prohibited. If you received this transmission in error, please
send
an electronic mail message to postmaster@xxxxxxxxxx so we may instruct you
regarding its disposition.
_______________________________________________
This is the System 21 Users (SYSTEM21) mailing list
To post a message email: SYSTEM21@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/system21
or email: SYSTEM21-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/system21.
As an Amazon Associate we earn from qualifying purchases.
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.
