|
View previous topic :: View next topic
|
| Author |
Message |
kumar1234
New User
Joined: 06 Nov 2007
Posts: 84
Location: bangalore
|
|
|
|
Hi All,
I have a proc with around 15 steps in it and my final aim is to get a report at the last step. When I run the job I get the required report but in a step in the middle I am getting 'file attribute mismatch' i.e.u4038. In that step it is showing in the input file where I have not done any changes and the record format is VB. Is it fine. Can anyone help me out in this.
thanks in advance. |
|
| Back to top |
|
 |
balakrishna reddy
Active User
Joined: 13 Jul 2007
Posts: 128
Location: Guntur
|
|
|
|
Hi Kumar,
| Quote: |
In that step it is showing in the input file where I have not done any changes
|
Can you provide us some details about what you are trying to do in that step and if possible specify the sysout of that job. |
|
| Back to top |
|
|
kumar1234
New User
Joined: 06 Nov 2007
Posts: 84
Location: bangalore
|
|
|
|
Hi,
We are trying to extract records in that particular step and some compute in the program. But in the input file I have not done any changes, it is the prduction input file and it is VB format.
This is the sysout message in that particular step.
"A file attribute mismatch was detected. File CLMMSTR-FILE in program had a record length of 940 and the file specified in the ASSIGN clause had a record length of 875".
thanks, |
|
| Back to top |
|
|
Aaru
Senior Member
Joined: 03 Jul 2007
Posts: 1287
Location: Chennai, India
|
|
|
|
Kumar,
| Quote: |
| A file attribute mismatch was detected. File CLMMSTR-FILE in program had a record length of 940 and the file specified in the ASSIGN clause had a record length of 875". |
This is self-explanatory. The record length specified in the JCL and in the File Division are different. Change accordingly.
what should be the record length of the final output file? |
|
| Back to top |
|
|
kumar1234
New User
Joined: 06 Nov 2007
Posts: 84
Location: bangalore
|
|
|
|
But I verified with my friend he is saying if I have not done any changes in prod file then leave it, dont do any changes since the record format of my input file is VB.
Thanks. |
|
| Back to top |
|
|
Aaru
Senior Member
Joined: 03 Jul 2007
Posts: 1287
Location: Chennai, India
|
|
|
|
Kumar,
If you have the source code check the record length specified in the FD DIVISION for CLMMSTR-FILE. It should be 936. (as VB)
Check the record length of the input file given across the DD. It would be 875 and hence the file attribute mismatch.
Just check and post your observations. |
|
| Back to top |
|
|
balakrishna reddy
Active User
Joined: 13 Jul 2007
Posts: 128
Location: Guntur
|
|
|
|
Hi Kumar,
Can you post the FD & FILE CONTROL of that variable file. |
|
| Back to top |
|
|
kumar1234
New User
Joined: 06 Nov 2007
Posts: 84
Location: bangalore
|
|
|
|
Aaru,
It is the same as you mentioned, now what do I need to do.
thanks, |
|
| Back to top |
|
|
Aaru
Senior Member
Joined: 03 Jul 2007
Posts: 1287
Location: Chennai, India
|
|
|
|
Kumar,
| Quote: |
| It is the same as you mentioned, now what do I need to do. |
Either you have change the record length in the cobol program and compile\link again.
or check whether you have got the correct input file.
Are you testing with the correct input file?
It all depends on your business requirements. |
|
| Back to top |
|
|
banu_parveen
New User
Joined: 30 Jan 2007
Posts: 6
Location: india
|
|
|
|
| For VB files the LRECL specified in the JCL should be plus four bytes to what is specified in the program. |
|
| Back to top |
|
|
|
|
