× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



This is what I see (showing both the good and bad)
-------------------
6 > strsql
5751 records copied to file QIBM_SFD in QTEMP.
6 > wrksplf
6 > strsql
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.

-----------------
F1 details on the Copy failure
-----------------

Message . . . . : Copy request failed for file QIBM_SFD in QTEMP.

Cause . . . . . : The file QIBM_SFD in library QTEMP specified in the TOFILE
parameter must be a double-byte character set (DBCS) file.
Recovery . . . : Change the TOFILE parameter, and try the command again.

---------------------------------
So the QIBM file needs to be defined as a double-byte file somehow?

Shane Reeves
Sr. Programmer
Summit Polymers- Technical Center

o. 269.324.9320 x50444
m. 269.217.4874

NOTICE: This e-mail message and any attachments are confidential and intended solely for use of the intended recipient. If you have received this e-mail in error, please delete this message. For purposes of engaging in binding contracts related to non-production goods and services with Summit Polymers, please refer to  Contracts for Non-Production Goods and Services.

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Javier Sanchez
Sent: Monday, October 7, 2024 10:55 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: SYSTOOLS.SPOOLED_FILE_DATA

CAUTION: This email originated from outside your organization. Exercise caution when opening attachments or clicking links, especially from unknown senders.


Can you check the job log of the connection you are using to issue these queries?
Are you using iACS?

JS

El lun, 7 oct 2024 a las 8:47, Shane Reeves (<SReeves@xxxxxxxxxxxxxxxxxx>)
escribió:

So, I'm trying out this SQL tool on the IBM

SYSTOOLS.SPOOLED_FILE_DATA



But I'm getting mixed results. Some spool files will show data, but
it seems like any 'QPRINT' file always comes back empty.



For example, I have these spool files



File

File Nbr Job User Number

QPUOPRTF 1 MISSR02 SREEVES 660572

MR134 1 MR134 SREEVES 660936

QPUOPRTF 11 MISSR01 SREEVES 656291

QPJOBLOG 1 QPADEV0093 SREEVES 660769

QPUOPRTF 1 MISSR02 SREEVES 702127

QPUOPRTF 2 MISSR02 SREEVES 702127

QPRINT 1 IVN104C SREEVES 702247



I'm able to retrieve the MR134 and the QPJOBLOG files for examples



SELECT *

FROM TABLE(SYSTOOLS.SPOOLED_FILE_DATA(

JOB_NAME => '660769/SREEVES/QPADEV0093'

SPOOLED_FILE_NAME => 'QPJOBLOG',

SPOOLED_FILE_NUMBER => 1))



Above works...



But when I try the same for the QPRINT



SELECT *

FROM TABLE(SYSTOOLS.SPOOLED_FILE_DATA(

JOB_NAME => '702247/SREEVES/IVN104C',

SPOOLED_FILE_NAME => 'QPRINT',

SPOOLED_FILE_NUMBER => 1))



It comes back with nothing.

Am I missing something? Is there something special with QPRINT files?



Thanks

Shane

--
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://linkprotect.cudasvc.com/url?a=https%3a%2f%2flists.midrange.com
%2fmailman%2flistinfo%2fmidrange-l&c=E,1,rw9FRy_ohfVFfyChykVvrHy040IIE
QCuoE6T4YNloZhn4nZmtKOs1GZTTn_qasHZlxAksKTPv0VmeTBpxTnSU1iNWcgGaAPXMHm
4CuoJDTfbFEo2WreA&typo=1 or email:
MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://linkprotect.cudasvc.com/url?a=https%3a%2f%2farchive.midrange.com%2fmidrange-l&c=E,1,7cVNwPMhZurS5mXkgloXMeIZa9SVfJWq_GIPCKGLSI--tAHH1QS0Ut0aJZIq6wV47ctvzdgP5TJTD4OjyJmWLTzr4DvkwuuwqVwdjqH6HO4A3Qw,&typo=1.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription
related questions.


--
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://linkprotect.cudasvc.com/url?a=https%3a%2f%2flists.midrange.com%2fmailman%2flistinfo%2fmidrange-l&c=E,1,Bv4R3SX0ObfhiPESr7Aal3xPfjv6y5beqQZSprwEQ6zv3YRnjZuMIW2Xf67TLEqrFPwp_HbZ6kVFHApwWYriJmvwsDq0xn6euN5DBNaS&typo=1
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at https://linkprotect.cudasvc.com/url?a=https%3a%2f%2farchive.midrange.com%2fmidrange-l&c=E,1,PE-RgBrhLMWaqbxhQR0M1zVE_dCxKshx15FvsskxyfGu5yMHGlxK7B1ELf14w_TaxDWIl9egt8NAhMBdpOHNjl3zdbyDNnDPSTRfaelSHv1LqHI1oQ,,&typo=1.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.