why I am getting only ascii characters in my output

xylene567 · New User Joined: 11 Jun 2007 Posts: 12 Location: TVM

Hi,
I am getting a warning code of 4 and I find this message in the spool.

INPUT STATEMENT WAS NOT A FULL SELECT ON A SINGLE TABLE. LOAD STATEMENT WILL NEED MODIFICATION.
UNLOAD DATA SET SYSREC00 RECORD LENGTH SET TO 6

I get only ASCII characters in my output file.

My code is as follows.

//***************************************************************
//* DATABASE OUTPUT FILE
//***************************************************************
//STEP010 EXEC PGM=IKJEFT1A,DYNAMNBR=20
//STEPLIB DD DISP=SHR,DSN=SYS4.DB2.P2D2.SDSNEXIT
// DD DISP=SHR,DSN=SYS4.DB2.P2D2.SDSNLOAD
//*
//SYSREC00 DD DSN=AXXXXX.DEL010.OUTDD2,
//*SYSREC00 DD DSN=*.DEL010.OUTDD1,
// DISP=(NEW,CATLG,DELETE),
// SPACE=(CYL,(150,75),RLSE),
// UNIT=SYSDA
//*
//SYSPUNCH DD DUMMY
//SYSTSPRT DD SYSOUT=*
//SYSPRINT DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//SYSTSIN DD *
. DSN SYSTEM(P2D2)
RUN PROGRAM(DSNTIAUL) PLAN(DSNTIAUL) PARM('SQL') -
LIB('SYS4.DB2.P2D2.RUNLIB.LOAD')
END
//*
//SYSIN DD *

SET CURRENT DEGREE = 'ANY';

SELECT A.AXX_ID_CHXXX
FROM D2XX.AXX_CHAIN_EOM_SHR A
,D2XXA.AXX_CHANL_REL B
WHERE A.AXX_ID_CXXX = B.AXX_ID_CXXX
FETCH FIRST 120 ROWS ONLY
;
// . . . . . . . . . . . . . . . . . . . . .

Can someone help me and tell me why I am getting only ascii characters in my output file?

William Thompson · Posted: Mon Oct 01, 2007 6:19 pm

Because the input is ASCII?

xylene567 · New User Joined: 11 Jun 2007 Posts: 12 Location: TVM

Nope I checked the tables using DB2 Tools. The data can be viewed with no probs there

dick scherrer · Posted: Mon Oct 01, 2007 6:27 pm

Hello,

What do you mean when you say

xylene567 · New User Joined: 11 Jun 2007 Posts: 12 Location: TVM

I got the output as
&<CCS
ë<CCS
Î CCS
the actual output has to be

504.
534.
760.
which are decimal numbers (11,0)
Is it the problem with some conversions? I am not sure if the output that I got is ASCII characters but then it doesnt look good !

Craq Giegerich · Posted: Mon Oct 01, 2007 7:12 pm

It could be packed decimal but without seeing the hex display it is hard to tell.

dick scherrer · Posted: Mon Oct 01, 2007 8:08 pm

Hello,

The unload used the attributes of the database fields. In your unloaded file, you have packed-decimal (comp-3) values that are perfectly valid.

You have not posted the data in hex. If you do, it will make more sense.

For example, the ampersand "&" is a hex 50. The "<" is hex 4C. There is your 504 in packed decimal (x'504C').

xylene567 · New User Joined: 11 Jun 2007 Posts: 12 Location: TVM

The output file in hex format !

dick scherrer · Posted: Mon Oct 01, 2007 9:23 pm

Hello,

When you post jcl, code, or data, it is a good ides to use the "Code" tab near the top of the reply panel. It preserves alignment and makes the info much more readable. Please note how your data looks now (i added the code tab).

What you have is valid packed-decimal (comp-3) output and that can be used directly in the process that will read the unloaded data (as long as the reading is done on the mainframe).

If this data is to be downloaded to some win-based or unix process, the packed-decimal data will not work.