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



Weird thing. Look at this:

https://www.ibm.com/support/pages/message-cpf3311-received-cpysplf-because-dbcs

On the other hand, a temp PF file QIBM_SPD is created in QTEMP to receive
the spooled file data as seen in the job log. The CRTPF command says that
if no DDS is specified, a record length must be specified, and a CCSID
65535 is by default given to that PF. The $1MM question is: why does it
work with the other spooled files?

Obviously there must be a difference on how they are generated related to
CCSID values present at that time.

Shane, please try this, I see you're using the green screen's STRSQL
command.

OVRPRTF FILE(QTEMP/QIBM_SPD) CHRID(*JOBCCSID) OVRSCOPE(*CALLLVL)

Then try again and see what happens. If it fails again, now change the
CHRID parameter to 65535 and retry.

The CCSID value is the problem here, either the spooled file's or the
job's, and with which on it was created.

JS


El lun, 7 oct 2024 a las 9:38, Rob Berendt (<robertowenberendt@xxxxxxxxx>)
escribió:

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.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.