|
View previous topic :: View next topic
|
| Author |
Message |
neoconvoy
New User
Joined: 22 Jul 2006
Posts: 9
|
|
|
|
I have a step that uses the input dataset's dcb as a model for an output dataset :
//input dd disp=shr,dsn=inputfile
//output dd disp=(new,catlg,delete),dsn=outfile,dcb=*.input,...
There is no problem when the program being executed is DFSORT.
But when I used an eztp program, it abends.
Is this saying that the above is not possible for user created programs like eztp or cobol, but works for DFSORT utilities ? |
|
| Back to top |
|
 |
expat
Global Moderator
Joined: 14 Mar 2007
Posts: 8797
Location: Welsh Wales
|
|
|
|
Please post your code and your output, as you have given us no information at all.
What was the abend, the program, type of datasets being used ...... etc. etc. |
|
| Back to top |
|
|
ofer71
Global Moderator
Joined: 27 Dec 2005
Posts: 2358
Location: Israel
|
|
|
|
Also, if you can post the actual JCL lines, it might be easier to help you.
O. |
|
| Back to top |
|
|
William Thompson
Global Moderator
Joined: 18 Nov 2006
Posts: 3156
Location: Tucson AZ
|
|
|
|
DFSORT is very smart...
| neoconvoy wrote: |
| But when I used an eztp program, it abends |
Show up again and show us what your problem is? Provide details.....  |
|
| Back to top |
|
|
neoconvoy
New User
Joined: 22 Jul 2006
Posts: 9
|
|
|
|
Here they are, but dataset and pgm names are masked out.
These are the jcl lines that are executed.
| Quote: |
//STEP020 EXEC PGM=eztppgm,COND=(0,NE)
//*
//infile DD DISP=SHR,DSN=infile
//outfile DD DSN=outfile,
// DISP=(NEW,CATLG,DELETE),
// SPACE=&SMALL,
// DCB=*.infile
//SYSPRINT DD SYSOUT=*
//SYSOUT DD SYSOUT=*
//* |
And this is the error returned.
| Quote: |
.IEC141I 013-34,IGG0191A,jobname,STEP020,infile,D4A5,EBPP70,infile
.IEA995I SYMPTOM DUMP OUTPUT
.SYSTEM COMPLETION CODE=013 REASON CODE=00000034
. TIME=03.42.41 SEQ=14910 CPU=0000 ASID=015B
. PSW AT TIME OF ERROR 075C1000 80D77906 ILC 2 INTC 0D
. NO ACTIVE MODULE FOUND
. NAME=UNKNOWN
. DATA AT PSW 00D77900 - 41003B62 0A0D41F0 38A656F0
. GR 0: 00D77BCC 1: A4013000
. 2: 000063B0 3: 00D7706A
. 4: 008CB410 5: 008CB7A4
. 6: 008CB74C 7: 008CB7A4
. 8: 008CB76C 9: 008B946C
. A: 00F23E20 B: 00000000
. C: 008CCF20 D: 000064AC
. E: 80D771A2 F: 00000034
. END OF SYMPTOM DUMP
.IEF472I jobname STEP020 - COMPLETION CODE - SYSTEM=013 USER=0000 REASON=000000 |
|
|
| Back to top |
|
|
neoconvoy
New User
Joined: 22 Jul 2006
Posts: 9
|
|
|
|
Sorry, this should be the correct error output:
The "infile" should be "outfile".
| Quote: |
.IEC141I 013-34,IGG0191A,jobname,STEP020,outfile,D4A5,EBPP70,outfile
.IEA995I SYMPTOM DUMP OUTPUT
.SYSTEM COMPLETION CODE=013 REASON CODE=00000034
. TIME=03.42.41 SEQ=14910 CPU=0000 ASID=015B
. PSW AT TIME OF ERROR 075C1000 80D77906 ILC 2 INTC 0D
. NO ACTIVE MODULE FOUND
. NAME=UNKNOWN
. DATA AT PSW 00D77900 - 41003B62 0A0D41F0 38A656F0
. GR 0: 00D77BCC 1: A4013000
. 2: 000063B0 3: 00D7706A
. 4: 008CB410 5: 008CB7A4
. 6: 008CB74C 7: 008CB7A4
. 8: 008CB76C 9: 008B946C
. A: 00F23E20 B: 00000000
. C: 008CCF20 D: 000064AC
. E: 80D771A2 F: 00000034
. END OF SYMPTOM DUMP
.IEF472I jobname STEP020 - COMPLETION CODE - SYSTEM=013 USER=0000 REASON=000000 |
|
|
| Back to top |
|
|
shankar.v
Active User
Joined: 25 Jun 2007
Posts: 196
Location: Bangalore
|
|
|
|
| Quote: |
.IEC141I 013-34,IGG0191A,jobname,STEP020,outfile,D4A5,EBPP70,outfile
.IEA995I SYMPTOM DUMP OUTPUT
.SYSTEM COMPLETION CODE=013 REASON CODE=00000034 |
The outfile DCB parameters in JCL doesn't coincide with the parameters specified in Easytrieve program.
If you post the Easytrieve program, it will be easier to help you. |
|
| Back to top |
|
|
shankar.v
Active User
Joined: 25 Jun 2007
Posts: 196
Location: Bangalore
|
|
|
|
| Confirm with the LRECL, BLKSIZE and RECFM from infile coincide with the parameters specified in easytrieve program for outfile. |
|
| Back to top |
|
|
expat
Global Moderator
Joined: 14 Mar 2007
Posts: 8797
Location: Welsh Wales
|
|
|
|
If you are changing the length of the record in any way, shortening or extending the line length, or writing out a different format, i.e. from FB to VB, or VB to FB, then you can not use the same attributes for the output file as the input file.
So, what is your program doing ??? |
|
| Back to top |
|
|
neoconvoy
New User
Joined: 22 Jul 2006
Posts: 9
|
|
|
|
| expat wrote: |
If you are changing the length of the record in any way, shortening or extending the line length, or writing out a different format, i.e. from FB to VB, or VB to FB, then you can not use the same attributes for the output file as the input file.
So, what is your program doing ??? |
The program is performing some checks and if necessary, overwrite a particular field, and write the record to the output file in the same format.
I did not define the record format of the output file in the EZTP program, and did a PUT OUTFILE FROM INFILE (after overwriting the INFILE field if necessary).
The definition of the file in EZTP:
FILE OUTFILE, that's all.
Based on the error message, I thought the EZTP program was not executed yet when the abend occurred. |
|
| Back to top |
|
|
|
|
