|
Given my current script:
-- BEGIN
Create or Replace table qtemp/WRKASP as (
select 1 as Seq, Current Server as Server, ASP_NUMBER, DEVD_NAME,
100 - ( Round( DEC(DEC(TOTAL_CAPACITY_AVAILABLE, 21, 3) /
DEC(TOTAL_CAPACITY, 21, 3) * 100, 21, 3), 2) ) as Pct_Used
from qsys2.asp_info ORDER BY Asp_Number
) WITH NO DATA;
Delete from qtemp/WRKASP ;
Insert into qtemp/WRKASP (
select 1 as Seq, Current Server as Server, ASP_NUMBER, DEVD_NAME,
100 - ( Round( DEC(DEC(TOTAL_CAPACITY_AVAILABLE, 21, 3) /
DEC(TOTAL_CAPACITY, 21, 3) * 100, 21, 3), 2) ) as Pct_Used
from ABCAA1.qsys2.asp_info ORDER BY Asp_Number);
Insert into qtemp/WRKASP (
select 2 as Seq, Current Server as Server, ASP_NUMBER, DEVD_NAME,
100 - ( Round( DEC(DEC(TOTAL_CAPACITY_AVAILABLE, 21, 3) /
DEC(TOTAL_CAPACITY, 21, 3) * 100, 21, 3), 2) ) as Pct_Used
from TAA01B.qsys2.asp_info ORDER BY Asp_Number);
(... repeat for 28 more servers.)
-- END
I would like to replace the Insert statements in the script to procedure
calls:
Call RetrieveASP (1, 'ABCAA1');
Call RetrieveASP (2, 'TAA01B');
...
Call RetrieveASP (30, 'FWC03A');
The question is, can the procedure take the second parameter and use it in
a 3-part file name. E.g., 'ABCAA1' > 'FROM ABCAA1.qsys2.asp_info'.
(The first parameter is the Seq value.)
I know I could do this in CL, building the SQL statement dynamically, but
I'd like to avoid CL if the SQL solution isn't too complicated. I have
several more scripts in the pipeline that will utilize the 3-part naming
for thirty servers.
*** CONFIDENTIALITY NOTICE: The information contained in this
communication may be confidential, and is intended only for the use of the
recipients named above. If the reader of this message is not the intended
recipient, you are hereby notified that any dissemination, distribution, or
copying of this communication, or any of its contents, is strictly
prohibited. If you have received this communication in error, please return
it to the sender immediately and delete the original message and any copy
of it from your computer system. If you have any questions concerning this
message, please contact the sender. ***
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.