Jim

Stored procedures - the SQL type - are made into C/C++ code and compiled - stored procedures are acutally ways to call programs from SQL. So these objects were created when the CREATE PROCEDURE was executed. This is done under the covers - generally we are not expected to deal with these objects, instead, use the DROP and CREATE again, as Elvis pointed out.

However, you CAN use these and move from one library to another. The most reliable way is the SAVOBJ/RSTOBJ that has been mentioned. See, these objects contain in their attributes the stored procedure information. When they are restored to another system of another library, entries will be placed into the SYSPROCS table, hence, doing the same thing as the CREATE statement does.

You should really read the redbook on all this - called "Stored Procedures, Functions..." or something like that - it's all well explained there.

Any errors in this comment are all mine own!

HTH
Vern

-------------- Original message --------------
From: JDHorn@xxxxxxxxxxxxxx

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 email is intended only for the person or entity
to which it is addressed and may contain information
that is privileged, confidential or otherwise protected
from disclosure. If you are not the named addressee
or an employee or agent responsible for delivering
this message to the named addressee, you are not
authorized to read, print, retain copy, and disseminate
this message or any part of it. If you have received this
message in error please notify us immediately by email,
discard any paper copies and delete all electronic files
of this message.


----------------------------------------------------------------------

message: 1
date: Wed, 10 Sep 2008 09:40:12 -0400
from: rob@xxxxxxxxx
subject: Re: MIDRANGE-L Digest, Vol 7, Issue 1803

The situation is that stored procedures, user defined functions, etc, do
NOT exist in
wrklnk '/qsys.lib/mylib.lib'
and also do not appear in a DSPOBJD. Therefore
A - Since they don't appear in a DSPOBJD they won't appear to "read
outfile"
B - Since they don't appear in wrklnk then CPY will have no effect.

They really only exist in SYSPROCS and SYSFUNCS.

Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
--
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 thread ...


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