Re: CLP to save just srcf files -- MIDRANGE-L

I've got it on V4R5.  Use it quite a bit.  It is real handy.


Nick



Nick Radich
Sr. Programmer/Analyst
EPC Molding, Inc.
Direct  (320) 679-6683
Toll free  (800) 388-2155  ext. 6683
Fax  (320) 679-4516
nick_radich@xxxxxxxxxxxxxx



jmmckee@xxxxxxxxxxxxxx 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
02/21/07 01:46 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
midrange-l@xxxxxxxxxxxx
cc

Subject
Re: CLP to save just srcf files






How far back was QSYS2/SYSTABLES first available?

John McKee

Quoting rob@xxxxxxxxx:

Why do step 1 when you already have a file that automatically has that
built in and is automatically updated - QSYS2/SYSTABLES?

I've seen files like this, maybe even the same name, on SQL Server.  I

say

use a standard dictionary file.

Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





"Steve Landess" <sjl_abc@xxxxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
02/21/2007 02:34 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
"Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
cc

Fax to

Subject
Re: CLP to save just srcf files






Al -

DSPFD works...

1) DSPFD FILE(YOURLIB/*ALL) TYPE(*BASATR) OUTPUT(*OUTFILE)
OUTFILE(QTEMP/FILES)

2) The outfile has a field (ATDTAT) which notes the type of file.
    (D=Data, S=Source)

3) Example SQL query of the outfile to show the source physical files:

    select ATFILE, ATLIB, ATFILA, ATDTAT
    from QTEMP/TEMP
    where ATDTAT = 'S'

- sjl


----- Original Message -----
From: "Al Barsa" <barsa@xxxxxxxxxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Wednesday, February 21, 2007 10:33 AM
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

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




            fbocch2595@xxxxxx
            m
            Sent by: To
            midrange-l-bounce         midrange-l@xxxxxxxxxxxx
            s@xxxxxxxxxxxx cc

Subject
            02/21/2007 09:37          CLP to save just srcf files
            AM


            Please respond to
            Midrange Systems
                Technical
               Discussion
            <midrange-l@midra
                nge.com>






Hi, I want to save all source files to a savf and I've got a pgm that

does

that by saving all files prefixed by Q* to a savf.  There are some PF's
that have files prefixed by Q so what's the best way to save only the
source files to the savf and not the PF's?

Thanks, Frank

p.s.  We don't have TAATOOLS which probably has something to do this.


________________________________________________________________________
Check out the new AOL.  Most comprehensive set of free safety and

security

tools, free access to millions of high-quality videos from across the

web,

free AOL Mail and more.
--
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.


--
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.