There are 2 ways to do SAVSYS without your personal presence, but
neither is actually non-interactive.
1. Run the SAVSYS from the console using the delay parm. You can also
write a CLP that you can CALL from the console that could take
appropriate control steps prior to the SAVSYS.
2. Replace the console with a PC which is equipped with twinax card,
'dumb' terminal emulation, a scheduler (or controlling pgm that can wait
til TIME=x), and a 5250 terminal scripting program (ScriptMate is one
that I am familiar with). If this PC is also equipped with PCAnywhere
(or the like), you ~could~ run console functions from home.
Dick Daniels
http://www.wynth.com/
Please tell me more about how to accomplish the first way you suggested. I
was under the understanding that all subsystem had to be down in order to do
a SAVSYS, therefore, if I was running a job in a job queue, even under the
QCTL SBS, it would be killed.
--
Thanks,
Chris Stamey
-----------------
M...@Stamey.nu
http://www.Stamey.nu
http://www.Farther.com/VBAnswerNetwork
Network Engineer
Windows NT Administrator
Aspiring AS400 Administrator
VB Developer
ASP and Web Developer
More to come...
-----------------
Richard Daniels wrote in message <36AB3874...@wynth.com>...
Chris,
it should be no problem to run the savsys command within a CL prog. I do my
whole backup in a quite similar way, i.e.:
SAVCFG DEV(*SAVF) SAVF(BACKUP/SYSCFG) CLEAR(*ALL)
SAVLIB LIB(&LIB) DEV(*SAVF) SAVF(BACKUP/&SAVEFILE) +
CLEAR(*ALL) SAVACT(*SYNCLIB) +
SAVACTWAIT(60) SAVACTMSGQ(CORDES) +
DTACPR(*YES)
I made an entry in the jobscheduler to run it automatically each night.
Olaf
-----------== Posted via Deja News, The Discussion Network ==----------
http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
Each PC need be only an old 386. These cost less than terminals these
days.
> Please tell me more about how to accomplish the first way you suggested. I
> was under the understanding that all subsystem had to be down in order to do
> a SAVSYS, therefore, if I was running a job in a job queue, even under the
> QCTL SBS, it would be killed.
If I write and compile a CLP named BUMYSYS (Backup My System), it might
include steps to
Assure that it is being run by someone like QSYSOPR
Assure that it is being run within the controlling subsystem
Wait until a particular date and time
Send messages to logged on users
do an ENDSYS
Monitor the QSYSOPR msgq to assure that the system is in
restricted condition
Do the SAVSYS
Bring back up the OS or PWRDWNSYS RESTART(*YES)
Now as long as I run it from the SYSTEM CONSOLE, and make sure that the
console does not get turned off, and make sure that the logged on
console is in a secure area, I can run BUMYSYS via the CALL command, and
walk out leaving the console interactive job to do the backup when
specified.
HTH :-) But, frankly, I prefer the second way: using scripted PC's.
Dick Daniels
http://www.wynth.com/
Use the save menu, GO SAVE, option 21. There is an field where you can
tell it when to start the save and some other options you need to set if
no one will be there.
Also, can can do a RTVCLSRC on the CL program, QMNSRBND, that gets run
from this menu option. Make any mods you want, then have your own
version. Mine is called SAVESYSTEM. It automatically delays till 1:00am
and does an IPL when it is done.
--
Charles Wilt
Miami Luken, Inc.
e-mail: charle...@worldnet.no.spam.att.net
--->remove the no.spam.
If you want to see what we did, shoot me a note.
Brian
Stamey wrote in message ...
>I'm very interested in the first way you suggested. My IBM business partner
>and I already discussed the emulator card and pc Anywhere, but I woul dhave
>to dedicate a separate PC for each of my 3 AS400s to do this.
>
>Please tell me more about how to accomplish the first way you suggested. I
>was under the understanding that all subsystem had to be down in order to
do
>a SAVSYS, therefore, if I was running a job in a job queue, even under the
>QCTL SBS, it would be killed.
>--
>Thanks,
>Chris Stamey
>-----------------
>M...@Stamey.nu
>http://www.Stamey.nu
>http://www.Farther.com/VBAnswerNetwork
>Network Engineer
>Windows NT Administrator
>Aspiring AS400 Administrator
>VB Developer
>ASP and Web Developer
>More to come...
>-----------------
>Richard Daniels wrote in message <36AB3874...@wynth.com>...
>>Stamey wrote:>
>>> Is there any way to do a SAVSYS non-interactively?
>>> I know I have to take down the sub-systems, all of them, but does the
>AS400
>>> have any way to run a batch job/CL program once this is done?
>>
Sorry to change the subject, but I tried to send this via e-mail but
none of the address below worked:
I happened to see a post of yours in an AS/400 newsgroup with the
following tagline:
>Chris Stamey
>-----------------
>M...@Stamey.nu
>http://www.Stamey.nu
>http://www.Farther.com/VBAnswerNetwork
>Network Engineer
>Windows NT Administrator
>Aspiring AS400 Administrator
>VB Developer
>ASP and Web Developer
>More to come...
>-----------------
If you have time, I'd appreciate your thoughts on this:
I work at a manufacturing plant with a 24/7 operation and the entire
plant operates on AS/400s with software developed internally. I have
years of experience with AS/400 operation, programming, and management
and believe that in many cases it is the best system available for
ease of development and reliability. For small systems, especially if
they need a good GUI I would probably develop on PCs and would
consider Visual Basic.
Our company has been purchased by another company that is developing
and buying packages to replace everything we have at all our plants.
They don't believe it is cost-effective to have on-site staff for
operations or programming. They are having a start-up vendor to
produce a company-wide manufacturing system that will tie into process
contol and control production tracking and shipping. The vendor only
knows Visual Basic and that's what it will be written in. Everything
will be run off of hundreds of PCs network connected. I don't know
for sure, but I'd guess the database will be SQL server and everything
will be run with NT.
With your background, do you think this is a practical solution for
such a large and critical system? I certainly have reservations,
although I've only played with Visual Basic. Is Visual Basic robust
enough and easy enough to program to handle high-volume access to a
database and not have problems with record locks, etc? To further
complicate matters, they have decided to develop some custom reports
in-house. Of course they don't have anyone that can do this. They
have asked me to do this; presumably before they eliminate me. I have
no idea how they'll make changes long-term. Do you feel like Visual
Basic is a good language to develop reports in? I have been reviewing
the VB manuals this weekend and it didn't look like it would be
anywhere as easy as producing RPG or COBOL reports.
I'd sure appreciate your opinion.
Joey Myers
jmy...@linknet.net
The most important thing to ask is WHERE have they done this
SUCCESSFULLY and compare their DOWNTIME with yours...
a "Start-up" software vendor CAN be made up of true professionals who may do
an excellant job. Look out that they do not spread themselves too thin on
other clients OR start moving in desks and family pictures to your Company.
I heard of a situation where a software vendor (who I understand had been
around a while) put in a "turn key" system. They appeared to bite off way
too much since the customer was the "largest they had worked with".
Initially bringing the system up took forever. Also, they did not
"translate" data from the IBM S/36, THEY HIRED PEOPLE TO RE-KEY the 5000
Customer Master records and all other data that the new system required.
This truly surprised me as the ability to translate data from the IBM S/36
to IBM AIX (UNIX) machine is readily available.
IMHO
You have used two words in the same sentence that do NOT go together...
PC and Critical.
I guess that these words CAN go together in the same sentence if you are
talking about a "critical failure". If you are running in an AS/400
remember the manufacturers' claimed uptime for AS/400 is 99.4+%. This is
about 4-6 hours "unexpected" downtime per year. I can't remember where I
read this but, SEEM TO RECALL that Windows NT claims 95-96 % uptime. That
can mean as much as 18 DAYS unexpected downtime per year.
There has been a technological advance in Win95. I believe the 5 was turned
to 8. While I believe that Microsoft is making their best effort to produce
a good product, there is no substitute for the years of evolution from the
System/3 to 32 to 34 to 36/38 and in 1988 to AS/400. Reliability has always
been a hallmark of the IBM product. IBM is darn expensive but it WORKS!
In some measure of balance, there are some things that a PC is ideally
suited for. I am using one now as a terminal to read the news. They make
pretty good terminals into UNIX and other real computer systems when you get
a quality emulator product. Except for the MAC, there is no substitute for
its graphics capabilities and diversity of available printer drivers.
HEY The PC plays pretty good GAMES also...
--
Robert Butram
http://www.butram.com
The opinion expressed here may NOT reflect
the reality experienced by others!
Joey Myers wrote in message <36acbe68....@news.linknet.net>...
>Chris,
Simply put, the console job continues running. If that job (which, of course,
is interactive) does a SAVSYS, either by command from a command line or by a
CALL to a program that executes SAVSYS, there's no problem.
True, you can't keep *batch* jobs running through an ENDSYS or ENDSBS *ALL
nor can you continue running interactive jobs anywhere outside of QCTL; but
the console job isn't batch. And if a program is CALLed, it's still not
batch. You'd have a problem if you tried to submit the CALL to a job queue,
but not if you simply CALL a program.
One question... do you really mean the SAVSYS command? If so, why a SAVSYS?
There's generally no point to running that command unless you've done a major
upgrade or possibly just installed a cume PTF package. This means it's only
done twice a year or so if you're fairly diligent. The SAVSECDTA and SAVCFG
commands give you what you need on a regular basis and neither requires the
system to be in restricted state.
Tom Liotta
In article <wYRq2.797$007.3...@firenze.visi.net>,
"Stamey" <sta...@REMOVEMEfarther.com> wrote:
> I'm very interested in the first way you suggested. My IBM business partner
> and I already discussed the emulator card and pc Anywhere, but I woul dhave
> to dedicate a separate PC for each of my 3 AS400s to do this.
>
> Please tell me more about how to accomplish the first way you suggested. I
> was under the understanding that all subsystem had to be down in order to do
> a SAVSYS, therefore, if I was running a job in a job queue, even under the
> QCTL SBS, it would be killed.
> --
> Thanks,
> Chris Stamey
> -----------------
> M...@Stamey.nu
> http://www.Stamey.nu
> http://www.Farther.com/VBAnswerNetwork
> Network Engineer
> Windows NT Administrator
> Aspiring AS400 Administrator
> VB Developer
> ASP and Web Developer
> More to come...
-----------== Posted via Deja News, The Discussion Network ==----------
tho...@inorbit.com wrote in message <78jgti$upv$1...@nnrp1.dejanews.com>...
True enough, but both SAVCFG & SAVSECDTA can save to savefiles which can be
saved along with SAVLIB, etc. Or they can be directed to the same tape device
and simply placed at the beginning of the SAVLIB, etc., tape. No need to
multiply tape volumes. And if they're done to savefiles, say, in a separate
user ASP, they might never even need to go to tape at all. I've found
savefiles for these to be extremely handy on a couple occasions over the
years.
Tom Liotta
In article <78krf5$74d$1...@ender.paccar.com>,
-----------== Posted via Deja News, The Discussion Network ==----------