Re: Using SQL to view a spoolfile

[Rob Berendt <robertowenberendt@xxxxxxxxx>]

I would suggest searching ptf cover letters for these messages but the PTF
cover letter system is so bolloxed up right now it is useless.

What I am going to suggest is similar to "take two aspirin and call me in
the morning".
Use SYSTOOLS.GROUP_PTF_CURRENCY
Once you are up to snuff, try again.
If it still fails, then
GO QMGTOOLS/MG
13. Check IBM for updated QMGTOOLS
If it updates, run it again.  I've seen it have to do a stair step upgrade
and the first step, while required, was disastrous if you used it for more
than getting to the next step.
1. System Snapshot, use defaults
Open a case with IBM.  Append the results from QMGTOOLS.  Either by
attaching it yourself to the case or by using 10. FTP data to IBM
Always send QMGTOOLS with a new case.  Always.  Failure to do so will
result in a delay while they ask for a listing of PTF's, etc.  All provided
by that snapshot.  Send a joblog too.  If you are using Run SQL Scripts
simply add
CL: DSPJOBLOG OUTPUT(*PRINT);
When you send in a joblog do not use PDF format.  IBM has tools they use to
look at joblogs and they were written before PDF was a thing.  Check that
option when you use iACS to download a spool file.

Those messages are not generally indicative of a user error.


On Wed, May 8, 2024 at 9:53 PM <smith5646midrange@xxxxxxxxx> wrote:

> I was attempting to use SQL to view a spoolfile.
>
>
>
> SELECT * FROM TABLE(SYSTOOLS.SPOOLED_FILE_DATA(
>             JOB_NAME          =>'412514/PECKM/R008CP0001',
>             SPOOLED_FILE_NAME =>'PRT008M'))
> ORDER BY ORDINAL_POSITION;
>
>
>
> It returns an empty result set and the following messages are in the
> joblog.
>
>
>
> Copy request failed for file QIBM_SFD in QTEMP.
> Trigger program or external routine detected an error.
> Trigger program or external routine detected an error.
> Message FAILURE ON CPYSPLF returned from SIGNAL, RESIGNAL, or RAISE_ERROR.
>
>
>
> I have verified the JOB_NAME and SPOOLED_FILE_NAME multiple times and they
> are correct.  The trigger program errors really don't tell me anything
> useful.  Any idea why I am getting the results that I am getting?
>
> --
> 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.