Re: Automate spool download using ACS

[Rob Berendt <robertowenberendt@xxxxxxxxx>]

Have you tried the old 'faking 3 part naming" technique?
https://www.linkedin.com/pulse/faking-3-part-naming-when-using-ibm-i-services-rob-berendt/?trackingId=PZwoPeySSb6Y%2B1QGJVzQPA%3D%3D
Faking 3-part naming when using IBM i services | LinkedIn
<https://www.linkedin.com/pulse/faking-3-part-naming-when-using-ibm-i-services-rob-berendt/?trackingId=PZwoPeySSb6Y%2B1QGJVzQPA%3D%3D>

On Fri, Mar 21, 2025 at 3:18 PM Dan Bale <dan.bale@xxxxxxxxxxxxxxxxxxxxx>
wrote:

> I've created several stored procedures to run queries using three-part
> naming to remote systems, but I haven't figured out how to use that to run
> commands on remote systems.  What am I missing?
>
> - Dan Bale
>
> -----Original Message-----
> From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Rob
> Berendt
> Sent: Friday, March 21, 2025 1:21 PM
> To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
> Subject: Re: Automate spool download using ACS
>
> I'd write a stored procedure looping through a cursor opened over
> https://www.ibm.com/docs/en/i/7.5?topic=services-output-queue-entries-view.
> ..
> for each selected row I'd pump it through something to do a
> - Create or clear a db2 work file (ie crtpf qtemp/spool rcdlen(150))
> - CPYSPLF to this file
> - CPYTOSTMF
>
> Quite easily done.  Really this stuff is so easy I've almost given up on
> CL instead of trying to shoehorn SQL into CL.  I just use Stored Procedures.
> Now, implementing that into your corporate change management system is a
> hoot.  The FNG's should pick up on this stuff easily enough.
>
> *** 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.