If you always follow that naming convention, you can change your script to
take advantage of it and always SAV/RST the USP_* objects instead of CPYing
them. This will ensure SQL catalogue is updated with the correct
information.

Elvis

Celebrating 11-Years of SQL Performance Excellence on IBM i, i5/OS and
OS/400
www.centerfieldtechnology.com


-----Original Message-----
Subject: Re: view sysprocs and library consolidation

Rob

I am not a a procedure expert but -

the person I am dealing with said he named his procedures starting with
USP_ in one of our production libraries.

when I did a dspobjd on the library then did the following query

SELECT ODOBNM, ODOBTP, ODOBAT FROM cat/dspobjd WHERE odobnm like
'%USP%'

I got the following results. which I thought were the procedures.

Object Object Object
Type Attribute
USP_C00001 *PGM CLE
USP_C00002 *PGM CLE
USP_G00001 *PGM CLE
USP_G00002 *PGM CLE
USP_T00001 *PGM CLE

are they something else?

when i use strpdm to view objects I get this

Work with Objects Using PDM
S1013BCA


Library . . . . . MIS_LIB Position to . . . . . . .
.
Position to type . . . .
.


Type options, press
Enter.
2=Change 3=Copy 4=Delete 5=Display
7=Rename
8=Display description 9=Save 10=Restore 11=Move
...


Opt Object Type Attribute
Text
USP_C00001 *PGM CLE SQL PROCEDURE
USP_CREATESALESTABLES
USP_C00002 *PGM CLE SQL PROCEDURE
USP_CLEANUP_TMPSALESDAT
USP_G00001 *PGM CLE SQL PROCEDURE
USP_GETSALESMENSUMMARIZ
USP_G00002 *PGM CLE SQL PROCEDURE
USP_GETSALESMENSUMMARIZ
USP_T00001 *PGM CLE SQL PROCEDURE
USP_TMPSALESDATA

these were copied with the cpy cmd and technique I descriped before.

thanks


Jim Horn



This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].