Thanks Nathan...I'll give this API a try.
According to IBM, the Program Associated Space is where SQL Stored Procedure references for the program are stored. We discovered this when our DR machine consistently had SQL SP's missing. During the Save/Restore process that occurs in most replication applications (iTera), a program is saved from the primary machine and restored to the target DR machine. Upon restore, the OS looks into the PAS to know to create stored procedure entries into the SYSROUTINE table on the DR machine.
It is possible to have more than one SQL SP associated with a given program. So PGMA has SQLSP1 in SCHEMA1 and SQLSP2 in SCHEMA2 stored in its PAS.
Due to the citation I referenced in the original posting, renaming PGMA to PGMB will rename the SYSROUTINE entries as well. So SQLSP1 and SQLSP2 are both renamed to PGMB in their respective schemas. Now, applications that are looking for SQLSP2 in SCHEMA2 will fail.
This is only my theory, but I need to test it and then find a means to preemptively predict it. I hope that your suggested API is the means for which I search.
Steve Needles
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Nathan Andelin
Sent: Thursday, September 11, 2014 10:47 AM
To: Midrange Systems Technical Discussion
Subject: Re: How to determine the SQL Stored Procedures that are "attached" to a *PGM object?
Is anyone aware of a mean to list the contents of the Program
Associated Space? Particularly, the list of Stored Procedures that might reside there?
Retrieve Program Associated Space (QCLRPGAS) API
But I don't see how the Program Associated Space has anything to do with your problem. What makes you think it has?
--
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 communication, including attachments, is confidential, may be subject to legal privileges, and is intended for the sole use of the addressee. Any use, duplication, disclosure or dissemination of this communication, other than by the addressee, is prohibited. If you have received this communication in error, please notify the sender immediately and delete or destroy this communication and all copies.
TRVDiscDefault::1201
midrange.com
