CS collections can also be tailored via iNav.
Go to Configuration and Service, then right click on Collection Services
and select Properties. The 'Data to Collect' tab is where you can
either select from 4 predefined levels of collection, or go the Custom
route and choose the metrics in which you're most interested.
We also do the standard 15-minute collection interval, with 24-hour
cycle and 7-day retention. Eats a fair amount of disk space, but having
the data readily at hand comes in very handy if performance ever takes a
sudden turn for the worse.
Steve
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
midrange-l-request@xxxxxxxxxxxx
Sent: Tuesday, August 26, 2008 10:29 AM
To: midrange-l@xxxxxxxxxxxx
Subject: MIDRANGE-L Digest, Vol 7, Issue 1707
Send MIDRANGE-L mailing list submissions to
midrange-l@xxxxxxxxxxxx
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.midrange.com/mailman/listinfo/midrange-l
or, via email, send a message with subject or body 'help' to
midrange-l-request@xxxxxxxxxxxx
You can reach the person managing the list at
midrange-l-owner@xxxxxxxxxxxx
When replying, please edit your Subject line so it is more specific than
"Re: Contents of MIDRANGE-L digest..."
*** NOTE: When replying to this digest message, PLEASE remove all text
unrelated to your reply and change the subject line so it is meaningful.
Today's Topics:
1. RE: Backup question (Chris Bipes)
2. RE: Backup question (Stefan Tageson)
3. RE: Backup question (John McKee)
4. RE: What should I say to a *nix community? (john e)
5. Re: Backup question (Brian Dolinar)
6. Re: Backup question (Jim Franz)
7. Re: MGTCOL size (smorrison@xxxxxxxxxxxxxxxxxxx)
8. Re: Backup question (Jim Franz)
----------------------------------------------------------------------
message: 1
date: Tue, 26 Aug 2008 07:23:54 -0700
from: "Chris Bipes" <chris.bipes@xxxxxxxxxxxxxxx>
subject: RE: Backup question
Off the top of my head you are missing SAVSECDTA - save security data.
Chris Bipes
Director of Information Services
CrossCheck, Inc.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of John McKee
Sent: Tuesday, August 26, 2008 7:01 AM
To: Midrange Systems Technical Discussion
Subject: Backup question
Our software package is provided by HBOC. They have a number of
commands that are based on IBM commands, with subtle changes. They
differentiate them by prefacing their versions with a 'B'.
Using their commands, a full save of the system was accomplished with
BBACKUP.
This command brings up a number of options. Ultimately, a set of user
defined commands is run. In our case, the commands were: SAVSYS,
SAVLIB, SAVDLO, and SAV, with appropriate options.
I was told that IBM pretty much demanded that Go SAVE option 21 be used
instead.
According to the command help, the only commands that appear different
are that the controlling subsystem is ended and restarted. That process
was performed by operators when BBACKUP command was used.
Is there something else that is going on that is different from the
scripted backup? One reason to ask is that the BBACKUP command logs
start and stop time of each step - which is sometimes an issue.
------------------------------
message: 2
date: Tue, 26 Aug 2008 16:30:33 +0200
from: "Stefan Tageson" <stefan.tageson@xxxxxxxxxxx>
subject: RE: Backup question
Off the top of my head you are missing SAVSECDTA - save security
data.
You may need savcfg as well,
Regards
Stefan Tageson
AddconIT AB
Cell : +46 (0) 732 36 99 34
stefan.tageson@xxxxxxxxxxx
-------------------- Internet e-Mail Disclaimer --------------------
This e-mail and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they are
addressed.
If you are not the intended recipient you are notified that any use,
disclosure, copying or distribution of the information is prohibited. In
such case, you should destroy this message and kindly notify the sender
by reply e-mail.The views expressed in this e-mail and any attachments
are personal and, unless stated explicitly, do not represent the views
of AddconIT. Furthermore, AddconIT will not be bound by this e-mail.
------------------------------
message: 3
date: Tue, 26 Aug 2008 09:58:04 -0500
from: John McKee <jmmckee@xxxxxxxxxxxxxx>
subject: RE: Backup question
I thought SAVSECDTA was essentially accomplished by the SAVSYS command.
At another job I had, on a daily basis we did SAVSECDTA and SAVCHGOBJ
(been a long time ago). But, weekly, SAVSYS, SAVLIB, SAVDLO.
John McKee
Quoting Chris Bipes <chris.bipes@xxxxxxxxxxxxxxx>:
Off the top of my head you are missing SAVSECDTA - save security
data.
Chris Bipes
Director of Information Services
CrossCheck, Inc.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of John McKee
Sent: Tuesday, August 26, 2008 7:01 AM
To: Midrange Systems Technical Discussion
Subject: Backup question
Our software package is provided by HBOC. They have a number of
commands that are based on IBM commands, with subtle changes. They
differentiate them by prefacing their versions with a 'B'.
Using their commands, a full save of the system was accomplished with
BBACKUP.
This command brings up a number of options. Ultimately, a set of user
defined commands is run. In our case, the commands were: SAVSYS,
SAVLIB, SAVDLO, and SAV, with appropriate options.
I was told that IBM pretty much demanded that Go SAVE option 21 be
used instead.
According to the command help, the only commands that appear different
are that the controlling subsystem is ended and restarted. That
process was performed by operators when BBACKUP command was used.
Is there something else that is going on that is different from the
scripted backup? One reason to ask is that the BBACKUP command logs
start and stop time of each step - which is sometimes an issue.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
http://archive.midrange.com/midrange-l.
------------------------------
message: 4
date: Tue, 26 Aug 2008 17:12:12 +0200
from: john e <jacobus1968@xxxxxxxxxxx>
subject: RE: What should I say to a *nix community?
I don't think that ROI is the problem.
Most companies, and specially IT managers, want to avoid risk.
It's better for them to spread costs over a long period (maintenance)
which is not very visible to upper management instead of taking the risk
to rewrite the app.
From: Jerry@xxxxxxxxxxxxxxx
To: midrange-l@xxxxxxxxxxxx
Date: Tue, 26 Aug 2008 09:01:53 -0500
Subject: RE: What should I say to a *nix community?
I did this for years for (what should have been) a simple invoice
print program. That is, whenever "new" stuff was needed, used CALL's to
RPG IV pgms. It got so convoluted from both the original poor design
and, then, from my mods. Eventually, they wanted a change that simply
could not (for 100% of the test cases) be shoe-horned into the existing
mishmash. At last, a golden opportunity (excuse) to re-write it the way
that (even in RPG II) would make more sense.
I once worked for a company where the core program was a 3000+
mainline program with illogical (i.e., confusing, hard to
follow/comprehend) GOTO's. When it bombed (on average once a week; twice
in the busy season), it took two people to debug it. I once suggested to
my boss (he and I were usually the ones that had to debug it) that the
best thing to do was put a match to it and start all over. He wouldn't
here of it. Later we started a new company that needed the same
function/program. Fortunately (!) we couldn't shoe-horn the new company
into the old code. It took me a week to design and flowchart it, a week
to code (in II). In the next three years it crashed once. Took us two
minutes to find and fix it. We spent much more than two weeks debugging
the earlier monolith; keeping it was a false ROI. I know that ten years
after I left the old spaghetti-coded piece of c**p was still in
production.
Jerry C. Adams
IBM System i Programmer/Analyst
B&W Wholesale
office: 615-995-7024
email: jerry@xxxxxxxxxxxxxxx
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of PaulMmn
Sent: Tuesday, August 26, 2008 7:43 AM
To: Midrange Systems Technical Discussion
Subject: Re: What should I say to a *nix community?
Some truly ugly code is like... well, it's so ugly that it either
should be scrapped, rewritten, or propped up so it keeps working.
Hoops?? I'd be willing to build a wall of 'custom interfaces' around
that piece of code to avoid having to touch it! I'd be willing to burn
my RPG debugging templates to avoid having to touch it!
This is -result- of "most software is continually modified." By people
who didn't understand the program, and just patched the 'bad parts.'
The problem is that if it works correctly, and if it is truly ugly, it
is dangerous to The Company to monkey with it.
That piece of ugly code is likely -filled- with important business
logic! Ideally, the logic should be extracted into a nice,
streamlined, well-designed, well-written, well-documented, easily
maintained module, that can be called from any program that needs to
use that logic. And that's one of those "Major Projects" that's nice
to dream about, but we -really- "need" to add that GUI interface to
the order entry system first...
--Paul E Musselman
PaulMmn@xxxxxxxxxxxxxxxxxxxx
At 8:16 AM -0400 8/26/08, Charles Wilt wrote (in part):
But most software is continually modified, thus there is indeed an ROI
for rewriting to make use of more modern and easier to maintain
techniques.
Imagine the ugliest piece of code you have to work with on a periodic
basis....
How much of a headache is that? How many hoops are you willing to jump
through to avoid having to change that legacy code.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
http://archive.midrange.com/midrange-l.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
http://archive.midrange.com/midrange-l.
_________________________________________________________________
De leukste online filmpjes vind je op MSN Video!
http://video.msn.com/video.aspx?mkt=nl-nl
------------------------------
message: 5
date: Tue, 26 Aug 2008 11:15:46 -0400
from: "Brian Dolinar" <brian.dolinar@xxxxxxxxxxx>
subject: Re: Backup question
Ah, good old HBOC aka McKesson Series aka Series 2000.
http://www.mckesson.com/en_us/McKesson.com/For%2BHealthcare%2BProviders/
Hospitals/Hospital%2BInformation%2BSystems/Series%2B2000.html
The only thing dumber than IBM changing the name of the platform every
so often is a software vendor who names their application uber-similar
to the server platform's then-name. It makes "Who's on First"-type
conversations like this possible
*ring ring*
There's a problem.
A problem with what?
Series.
Huh? You mean the AS/400?
Yeah, Series.
Is there an issue with the Series i hardware?
Dunno, but there is this message on the screen...
Or do you mean a problem within the Series 2000 software?
Well, the message says "Series" in it...
*pounds head* If it could get the marketing clowns from McKesson and
IBM in a dark alley...
Sorry for the diversion, back to the OP's question:
BBACKUP is just a series of wrappers around the actual IBM save
commands.
We do our SAVSYS outside of the BBACKUP, after manually shutting down
the interfaces and updater threads from within the Series application
menus. Then you can either do a GO SAVE, 21 or your own CL commands or
program to do ENDSBS, SAVSYS, etc...
The rest of the backups are done by modifying the BSYDTAA/BSYSSVU file,
which can be accessed using mnemonic SSCM from inside the McKesson
Series software application. Where it made sense and was
straightforward saves, we just added the IBM commands to the file.
Where it didn't, we called a CLP program with the save commands and some
additional logic.
My 2 cents - I would prefer applications to just stick to
um...applications stuff and leave the backup and recovery outside.
Because when the feces strikes the AMD (air moving device), it is lots
easier to look at a few CL programs with commands that any AS/400 person
can read and understand to find out what was saved and how it was done,
instead of wading thru application menus, screens, tables and logs.
Brian Dolinar.
"John McKee" <jmmckee@xxxxxxxxxxxxxx> wrote in message
news:mailman.6408.1219759302.2545.midrange-l@xxxxxxxxxxxxxxx
Our software package is provided by HBOC. They have a number of
commands that
are based on IBM commands, with subtle changes. They differentiate
them by
prefacing their versions with a 'B'.
Using their commands, a full save of the system was accomplished with
BBACKUP.
This command brings up a number of options. Ultimately, a set of user
defined
commands is run. In our case, the commands were: SAVSYS, SAVLIB,
SAVDLO, and
SAV, with appropriate options.
I was told that IBM pretty much demanded that Go SAVE option 21 be
used instead.
According to the command help, the only commands that appear different
are that
the controlling subsystem is ended and restarted. That process was
performed
by operators when BBACKUP command was used.
Is there something else that is going on that is different from the
scripted
backup? One reason to ask is that the BBACKUP command logs start and
stop time
of each step - which is sometimes an issue.
Thanks,
John McKee
------------------------------
message: 6
date: Tue, 26 Aug 2008 11:17:01 -0400
from: "Jim Franz" <franz400@xxxxxxxxxxxx>
subject: Re: Backup question
This is from the V5R4 Help text for Save 21:
Runs the following commands:
ENDSBS SBS(*ALL) OPTION(*IMMED)
SAVSYS
SAVLIB LIB(*NONSYS) ACCPTH(*YES)
SAVDLO DLO(*ALL) FLR(*ANY)
SAV OBJ(('/*') ('/QSYS.LIB' *OMIT)
('/QDLS' *OMIT)) UPDHST(*YES)
STRSBS SBSD(controlling-subsystem)
The SAVSYS help text notes this:
The Save System (SAVSYS) command saves a copy of the Licensed Internal
Code and the QSYS library in a format compatible with the installation
of the operating system. It does not save objects from any other
library. In addition, it saves security and configuration objects that
can also be saved using the Save Security Data
(SAVSECDTA) and Save Configuration (SAVCFG) commands.
hth
Jim Franz
----- Original Message -----
From: "John McKee" <jmmckee@xxxxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Tuesday, August 26, 2008 10:00 AM
Subject: Backup question
Our software package is provided by HBOC. They have a number of
commands
that
are based on IBM commands, with subtle changes. They differentiate
them
by
prefacing their versions with a 'B'.
Using their commands, a full save of the system was accomplished with
BBACKUP.
This command brings up a number of options. Ultimately, a set of user
defined
commands is run. In our case, the commands were: SAVSYS, SAVLIB,
SAVDLO,
and
SAV, with appropriate options.
I was told that IBM pretty much demanded that Go SAVE option 21 be
used
instead.
According to the command help, the only commands that appear different
are
that
the controlling subsystem is ended and restarted. That process was
performed
by operators when BBACKUP command was used.
Is there something else that is going on that is different from the
scripted
backup? One reason to ask is that the BBACKUP command logs start and
stop
time
of each step - which is sometimes an issue.
Thanks,
John McKee
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
------------------------------
message: 7
date: Tue, 26 Aug 2008 10:22:47 -0500
from: smorrison@xxxxxxxxxxxxxxxxxxx
subject: Re: MGTCOL size
Rob,
The way I know how to do this is (gasp) green screen.
Go Perform
2 - Collect performance data
2 - Configure performance collection
Ours is set to collect data every 15 minutes, cycle the collection every
24 hours, and save the data for 7 days.
Steve
Steven Morrison
Fidelity Express
rob@xxxxxxxxx
Sent by: midrange-l-bounces@xxxxxxxxxxxx
08/26/2008 09:39 AM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
To
midrange-l@xxxxxxxxxxxx
cc
Subject
MGTCOL size
Management Central is collecting performance data into QMPGDATA as
*MGTCOL
objects. Are there settings to control the size? Like, not collect
this
or that, or, performance interval?
Object
Object Type SIZE DATE
---------- -------- --------------------------- ------
Q238000025 *MGTCOL 9,577,639,936 080825
Q237000025 *MGTCOL 9,354,293,248 080824
Q236000024 *MGTCOL 8,956,882,944 080823
Q239000025 *MGTCOL 4,695,732,224 080826
Rob Berendt
midrange.com
