RE: CLP to save just srcf files

Instead of doing DSP***, you can just do a query over one of the system
cross reference files that's in QSYS. I don't have the name off hand,
but it was discussed before on the list a few days ago... 

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Al Barsa
Sent: Wednesday, February 21, 2007 10:33 AM
To: Midrange Systems Technical Discussion
Subject: Re: CLP to save just srcf files


Hi,

TAA doesn't have what you want, but it could (within the limits I note
below).

There's nothing to say that a source file has to start with a Q
(although that's very typical), but with that said, it does have a
*OBJTYPE of something like PF-SRC (there is a System/38 variations)
object type, but not a complicated difference.  Although it would not be
as efficient as you like (to be polite), you could do a DSPOBJD
(library-name)/*ALL *FILE to an output file, and then OPNQRYF to find
the source files.  *YUK.  DSPFD should have something comparable that
would run faster, but I don't think (and rightly so) that it's high on
IBM list of desired enhancements.

Limitations:  300 objects per library, and one library to a save file.
(There's an exception to get more than 300 libraries to a Save
operation, but not a SAVF.  SAVF's are only library per save operation.
SAVLIB has a complicated exception that let';s you go past the 300
limit, and I betcha there's something comparable to SAVOBJ, but than
that tells me that your
system's isn't set up well.)   You could get around this with virtual
tape,
but it's really *COMPLICATED. and I suspect you wouldn't be happy.
(Like
being on the Titanic.)   There's a TAATOOL to help with virtual tape,
and
that just a little less complicated than relativity, and plausibly
warmer than the water where the Titanic sunk.

Bad news:  DSPOBJD would take longer than it took for the Titanic to
sink.
after first spotting the first iceberg.  (A bigger rudder would have
helped a lot, but I'm just a boat guy.)

Good news:  The inherent overlap in the save architecture would make it
seem that the save itself goes really fast, even faster than the Titanic
than was the sinking of the Thresher (you'd have to be over 50 to
remember that one, and not very wall documented as that was a
submarine).

Suggestions:
o     Put all your source files in one library:  (A really good
suggestion
if I say so myself, I'm sure someone will argue with me on this, and
then tell them something about the horse they rode in on.)  A reasonable
caveat would be one library per application.  For example mixing AR and
AP would likely be bad.
o     All (realistic)  limitations (including 300 object save limit and
the
speed of DSPOBJD) go away.  In this environment, there are limits, but
they are *REALLYHIGH.
o     By all comparison's save is really fast  in this environment.  An
overlap structure was built into it early in the System/38, and as long
as your objects are not hugely different in size (source typically
isn't), life is happy.
o     When the building fire alarm go's off, you know what to save
immediately, and SAVLIB and better yet SAVCHGOBJ would run light greased
lightning.

Al

Al Barsa, Jr.
Barsa Consulting Group, LLC

400>390

"i" comes before "p", "x" and "z"
e gads

Our system's had more names than Elizabeth Taylor!

914-251-1234
914-251-9406 fax

http://www.barsaconsulting.com
http://www.taatool.com
http://www.as400connection.com