|
Hi Rob,--
I tried what you said.
OVRPRTF FILE(QTEMP/QIBM_SPD) CHRID(*JOBCCSID) OVRSCOPE(*CALLLVL)
- doesn't allow the qualified 'QTEMP' but removing that OVRPRTF
FILE(QIBM_SPD) CHRID(*JOBCCSID) OVRSCOPE(*CALLLVL) Still the same
error
It sounds like you wanted me to try
OVRPRTF FILE(QIBM_SPD) CHRID(65535) OVRSCOPE(*CALLLVL) But I get
"Numeric value for parameter CHRID is not valid."
I couldn't get 65535 to work. But after prompting I tried using 836
because our Chinese environment uses that. I wasn't sure on the code
page -but selected 1....
OVRPRTF FILE(QIBM_SPD) CHRID(836 1) OVRSCOPE(*CALLLVL) This 'ran', but
still no improvement on the results.
I also tried WRKUSRJOB to change my running job and tested with both
CCSID as 65535 as well as 836. In both the same error came up.
I also tried changing the CCSID of QIBM_SPD in QTEMP but it appears it
recreates each run, as it switched it back to 37 when I ran the SQL again.
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
Javier Sanchez
Sent: Monday, October 7, 2024 12:11 PM
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.
Weird thing. Look at this:
https://www.ibm.com/support/pages/message-cpf3311-received-cpysplf-bec
ause-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?https://linkprotect.cudasvc.com/url?a=https%3a%2f%2farchive.midrange.c
"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-t
ab
le-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 IBMlist
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
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
.c
om%2fmailman%2flistinfo%2fmidrange-l&c=E,1,P861gp8Hwm2Zv_JU53SoEbp
dv
l4NMw5PxLEQAug0QywK-nL9cFugllH9MPU6-Z-GN5wNjre3nRkEJwKnsnmfpYW6zxT
Za
gt-PuIYJD0QD-tRgHGuosUVew,,&typo=1
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
om%2fmidrange-l&c=E,1,6EIllFVAfzx36nOUIGBbEhzrb8espLK-rTESEM9dATLldKig
a2s-iKglxuKh5CjDhx0UJccIHK1lbsbOaA61_ovp5QtLk54vTcRytc112Jc3GoF6PImTRh
I,&typo=1
.
https://linkprotect.cudasvc.com/url?a=https%3a%2f%2farchive.midrange.c--
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.c
om
%2fmailman%2flistinfo%2fmidrange-l&c=E,1,pNZIkmn7L7UFft5lt0o2vK6knG4
wG
YSGiNaMlcPmKkMs7D-ti17HGQp9DAKSTXc4SucjrBBTxY6kLjqa87BLuGk7k6J96IGoe
SE
JPaTIXZIT&typo=1 or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
om%2fmidrange-l&c=E,1,-Vt-d_QxbDktNa6sGIZyNgL-PRXw_tHxP9z6ZpEa94JncWJm
36TE7U0u1iOEpyx3pJkSHYxuWEXbUtDPBABb5g2R33lQ_bFUQ-zmymFI2_l9Mnc4wcA,&t
ypo=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,0GByhhMAl0kOCbELsOuc3WBUituhz
8Xe0X8fgRudOO9hZltzpjXlQd5CFyiQDGgyPC9KbCnhI4Zf-QjfZBY7NdQb9Aure4SvMmJ
2vNZwND_Big,,&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.c
om%2fmidrange-l&c=E,1,KnfjHXfOBRpuI9BNP7El_V5n_oxW9Lp_2uxBeSl4wdE6bJWn
1KMTCzqx2YPtTdDPlMDUPabptT9A2kXUCKb15Urv0MI-FuisNWvPIYJ8OdaYFvU,&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,YBNgP2B-kQMxACodBrL-54hHtzAMR
fUITVWTlgamdrerkshIUHaefCLfNEa0ZF00p3_kQUbg3Drp_NwLaU5sdlpSEvUdlBcTvFl
9rZSIBo1VRakh&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,RL4MUIrOtAIN67IyfpCR8AQHXynYV26uo0PKQyTiTGyJx0kI0ZNUNRrRckqsK2M-oxsVSna3qCnHZFabTzIT2ahOgecB3w_fgC5o7QYI&typo=1.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription
related questions.
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
