RE: Library and Source File Question

[rob@xxxxxxxxx]

Names that reflect the source types?
like
ORD500R for rpg
ORD500C for CL
ORD500D for display file
ORD500O for printer output?
And if you do a WRKLNK '/QSYS.LIB/MYLIB.LIB/ORD500*.*' you'll see:
/QSYS.LIB/MYLIB.LIB/ORD500C.PGM
/QSYS.LIB/MYLIB.LIB/ORD500D.FILE
/QSYS.LIB/MYLIB.LIB/ORD500O.FILE
/QSYS.LIB/MYLIB.LIB/ORD500R.PGM
And if you do a WRKOBJ MYLIB/ORD500* you'll see:
Object      Type      Library     Attribute
ORD500C     *PGM      MYLIB       CLP
ORD500R     *PGM      MYLIB       RPG
ORD500D     *FILE     MYLIB       DSPF
ORD500O     *FILE     MYLIB       PRTF

Question, when you create stuff on your PC do you end up with names like:
MYPGMEXE.EXE
TESTDOC.DOC
QUESTIONSDOC.DOC
OTHERDOC.DOC
FINANCIALSXLS.XLS
RESUMEWP1.WP1


Rob Berendt
--
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
Benjamin Franklin



                      Vernon Hamberg
                      <vhamberg@attbi.co        To:       
midrange-l@midrange.com
                      m>                        cc:
                      Sent by:                  Fax to:
                      midrange-l-admin@m        Subject:  RE: Library and 
Source File Question
                      idrange.com


                      10/05/2002 01:23
                      AM
                      Please respond to
                      midrange-l






Have separate source members. It did not used to be necessary, but
nowadays, because of record lengths, it is. RPGLE needs a record length of
112,  older RPG needs 92. QMQRY's need 91, QMFORMs need 162 or some such.

I would still use distinct names, even in separate source files, since the
resulting objects, whether modules or programs or service programs, still
need distinct names. This gives you the chance to make names that reflect
the original source types - might be useful.

Regards

Vern

At 10:25 AM 10/3/02 -0400, you wrote:
>Rusty,
>
>1)  At our shop we keep the objects and data in separate libraries
>     in the event we need to do special restores/backups. Our source
>     files are also stored in the object library.
>
>2)  We also keep all of our source code in a singe source-PF.
>     This does mean you should have a solid naming convention
>     for all of your member types so that they can be resident
>     in the same source file.  What I like about this is that
>     you can use PDM to see *all* of your source in the list at
>     one time.
>
>Good Luck,
>Terry

_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.