Re[2]: SYSTOOLS.SPOOLED_FILE_DATA

Rob, you would be completely shocked at the number of systems that still use the default 65535.
Since you like to keep at the first 1% of early adopters I can see why you might think the default is abnormal. It's not.



--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


------ Original Message ------

From "Rob Berendt" <robertowenberendt@xxxxxxxxx>

To "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxxxxxxxx>
Date 10/7/2024 10:37:26 AM
Subject Re: SYSTOOLS.SPOOLED_FILE_DATA

Oh my, someone who still uses CCSID=65535?
"If the spooled file contains double byte data, the job CCSID must be a
mixed CCSID."
https://www.ibm.com/docs/en/i/7.5?topic=services-spooled-file-data-table-function

On Mon, Oct 7, 2024 at 10:47 AM Shane Reeves <SReeves@xxxxxxxxxxxxxxxxxx>
wrote:

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://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.

--
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.