IBM Mainframe Forum

by **BillyBoyo** » Thu Nov 01, 2012 5:59 am

I get the same message using Fixed input files. Please post all of your sysout for the step.

by **porwalrox** » Thu Nov 01, 2012 11:28 am

ICE411I 0 THIS IS THE JOINKEYS MAIN TASK FOR JOINING F1 AND F2
ICE416I 0 JOINKEYS IS USING THE F1 SUBTASK FOR IN1 - SEE JNF1JMSG MESSAGES
ICE416I 1 JOINKEYS IS USING THE F2 SUBTASK FOR IN2 - SEE JNF2JMSG MESSAGES
ICE419I 0 JOINED RECORDS: TYPE=F, LENGTH=160
ICE201I H RECORD TYPE IS F - DATA STARTS IN POSITION 1
ICE805I 1 JOBNAME: U299060A , STEPNAME: STEP
ICE802I 0 BLOCKSET TECHNIQUE IN CONTROL
ICE143I 0 BLOCKSET COPY TECHNIQUE SELECTED
ICE250I 0 VISIT http://www.ibm.com/storage/dfsort FOR DFSORT PAPERS, EXAMPLES AN
ICE000I 1 - CONTROL STATEMENTS FOR 5694-A01, Z/OS DFSORT V1R12 - 11:18 ON THU NO
JOINKEYS F1=IN1,FIELDS=(1,7,A)
JOINKEYS F2=IN2,FIELDS=(1,7,A)
REFORMAT FIELDS=(F1:1,80,F2:1,80)
JOIN UNPAIRED,F1,F2
OPTION COPY
OUTFIL FNAMES=OUT,BUILD=(1,80,11,80)
ICE411I 0 THIS IS THE JOINKEYS MAIN TASK FOR JOINING F1 AND F2
ICE416I 0 JOINKEYS IS USING THE F1 SUBTASK FOR IN1 - SEE JNF1JMSG MESSAGES
ICE416I 1 JOINKEYS IS USING THE F2 SUBTASK FOR IN2 - SEE JNF2JMSG MESSAGES
ICE419I 0 JOINED RECORDS: TYPE=F, LENGTH=160
ICE201I H RECORD TYPE IS F - DATA STARTS IN POSITION 1
ICE043A 9 INVALID DATA SET ATTRIBUTES: OUT RECFM - REASON CODE IS 14
ICE751I 0 C5-K62149 C6-K90026 C7-K58148 C8-K67572 E9-K60824 E7-K70685
ICE052I 3 END OF DFSORT

by **BillyBoyo** » Thu Nov 01, 2012 2:32 pm

Select all

ICE419I 0 JOINED RECORDS: TYPE=F, LENGTH=160

The only way you'll get an F REFORMAT record with what you have coded is with at least F1 being Fixed.

by **porwalrox** » Thu Nov 01, 2012 2:59 pm

But even if i indicating my files are of type V.

Select all

JOINKEYS F1=IN1,FIELDS=(1,7,A),TYPE=V
JOINKEYS F2=IN2,FIELDS=(1,7,A),TYPE=V

I am getting same error & same reason code. & My both input files are of type V. My outfile is also of Type V.

by **porwalrox** » Thu Nov 01, 2012 3:14 pm

What i have done? I am telling you that first i have created two input files & one output file by using 3.2 & RECFM=V. Then i have inserted the data into those files. After that i am using the code which i have posted.
If somewhere i've made the mistake, please let me know.

by **Robert Sample** » Thu Nov 01, 2012 5:10 pm

I am telling you that first i have created two input files & one output file by using 3.2 & RECFM=V.

So what? The SYSTEM is telling you the files are fixed length -- and I am going to believe the system a whole lot more than anything you say. The computer does not lie to you. You may THINK you created variable length records, but somehow something has converted them to fixed length.

Furthermore, if you are dealing with variable length files, why are you not starting your records at position 5 to bypass the record descriptor word -- the way the SORT manuals tell you to?

by **NicC** » Thu Nov 01, 2012 6:17 pm

Use 3.2 or 'I' against the datasets in 3.4 and show us the results.

by **BillyBoyo** » Thu Nov 01, 2012 7:36 pm

I can only echo Robert and Nic and repeat what I said before.

No matter what you think, your F1 dataset, at least, is Fixed-length, not variable.

If you look up what TYPE=V does, you'll know you can safely delete it until you need it for a completely different situation.

by **porwalrox** » Fri Nov 02, 2012 11:35 am

Hi NicC!

Select all

Data Set Name . . . . : U299060.JN2FL1.PS

General Data Current Allocation
Management class . . : **None** Allocated blocks . : 78
Storage class . . . : STANDARD Allocated extents . : 1
Volume serial . . . : DTWK06
Device type . . . . : 3390
Data class . . . . . : **None**
Organization . . . : PS Current Utilization
Record format . . . : V Used blocks . . . . : 4
Record length . . . : 80 Used extents . . . : 1
Block size . . . . : 84
1st extent blocks . : 78
Secondary blocks . : 20 Dates
Data set name type : Creation date . . . : 2012/11/02
SMS Compressible. . : NO Referenced date . . : 2012/11/02
Expiration date . . : ***None***

Is something wrong here?

by **porwalrox** » Fri Nov 02, 2012 12:04 pm

If i code:

REFORMAT FIELDS=(F1:5,76,F2:5)
JOIN UNPAIRED,F1,F2
OPTION COPY
OUTFIL FNAMES=OUT,BUILD=(5,80,85,80)

Problem TYPE=F has been solved. Now i am getting only one problem in SYSOUT

Select all

ICE411I 0 THIS IS THE JOINKEYS MAIN TASK FOR JOINING F1 AND F2
ICE416I 0 JOINKEYS IS USING THE F1 SUBTASK FOR IN1 - SEE JNF1JMSG MESSAGES
ICE416I 1 JOINKEYS IS USING THE F2 SUBTASK FOR IN2 - SEE JNF2JMSG MESSAGES
ICE412A 0 REFORMAT REQUIRES RDW IN FIRST FIELD
ICE751I 0 C5-K62149 C6-K90026 C7-K58148 E7-K70685
ICE052I 3 END OF DFSORT

But If i put REFORMAT FIELDS=(F1:5,76,F2:5,76) like this again I have got the same TYPE=F problem.

Select all

ICE419I 0 JOINED RECORDS: TYPE=F, LENGTH=152
ICE201I H RECORD TYPE IS F - DATA STARTS IN POSITION 1

I think, i am doing some mistake in the REFORMAT FIELDS. Thanks Robert, Billy, NicC!

IBM Mainframe Forum

Merging two VB files to VB file

Re: Merging two VB files to VB file

Re: Merging two VB files to VB file

Re: Merging two VB files to VB file

Re: Merging two VB files to VB file

Re: Merging two VB files to VB file

Re: Merging two VB files to VB file

Re: Merging two VB files to VB file

Re: Merging two VB files to VB file

Re: Merging two VB files to VB file

Re: Merging two VB files to VB file