|
View previous topic :: View next topic
|
| Author |
Message |
Douglas Wilder
Active User
.jpg)
Joined: 28 Nov 2006
Posts: 305
Location: Deerfield IL
|
|
|
|
I had CBLCNVRT working to convert COBOL copybooks to Easytrieve a couple years ago not now it is giving errors as follows:
| Code: |
143 DEPENDING_ON_NAME * 40 A
143 *******B055 INVALID LENGTH, TYPE OR DECIMAL PLACES - 40
1202 MOVE WORD TO DEPENDING_ON_NAME
1202 *******B082 NAME IS UNDEFINED - DEPENDING_ON_NAME
*******A014 PREMATURE TERMINATION DUE TO PREVIOUS ERROR(S)
|
We have the following COBOL:
PP 5655-G53 IBM Enterprise COBOL for z/OS 3.3.1
| Code: |
JCL:
//STEP02 EXEC PGM=EZTPA00
//STEPLIB DD DSN=hlq.EASYPLUS,DISP=SHR
//EZTVFM DD UNIT=SYSDA,SPACE=(CYL,(5,5))
//SYSPRINT DD SYSOUT=*
//GLOSTAB DD DSN=userid.GLOSSARY.TABLE,DISP=SHR
//PANDD1 DD DSN=hlq.PANAUDIT.PLUS30C.PANLIB,DISP=SHR
//EASYPGM DD DSN=userid.CBLCNVRT.OUTPUT,DISP=(NEW,CATLG),
// DCB=(LRECL=80,RECFM=FB,BLKSIZE=0),
// UNIT=SYSDA,SPACE=(CYL,(30,30),RLSE)
//SYSIN DD *
%CBLCNVRT GLOSTAB COBOL II12 |
Does anyone see what I am doing wrong? |
|
| Back to top |
|
 |
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19243
Location: Inside the Matrix
|
|
|
|
Hello,
Try changing this
| Code: |
| %CBLCNVRT GLOSTAB COBOL II12 |
to
| Code: |
| %CBLCNVRT GLOSTAB COBOL I320 |
or
| Code: |
| %CBLCNVRT GLOSTAB COBOL I341 |
These are for the 3.2 and 3.4 compiler. I don't seen an entry for the 3.3 compiler, so hopefully, one of those will work for you.
Good luck and let us know what happens  |
|
| Back to top |
|
|
Douglas Wilder
Active User
Joined: 28 Nov 2006
Posts: 305
Location: Deerfield IL
|
|
|
|
%CBLCNVRT GLOSTAB COBOL I340
58 DEVICE_TYPE_OUT 46 8 A
*******B006 MACRO SYSTEM - PAN , PM007 PANDD1*CBLSI340 NOT FOUND
59 %CBLSI340 GLOSTAB
*******B076 REMAINDER OF STATEMENT IS IGNORED
%CBLCNVRT GLOSTAB COBOL I320
58 DEVICE_TYPE_OUT 46 8 A
*******B006 MACRO SYSTEM - PAN , PM007 PANDD1*CBLSI320 NOT FOUND
59 %CBLSI320 GLOSTAB
*******B076 REMAINDER OF STATEMENT IS IGNORED
60 FILE DDINFO F (52) VIRTUAL RETAIN
%CBLCNVRT GLOSTAB COBOL I330
58 DEVICE_TYPE_OUT 46 8 A
*******B006 MACRO SYSTEM - PAN , PM007 PANDD1*CBLSI330 NOT FOUND
59 %CBLSI330 GLOSTAB
*******B076 REMAINDER OF STATEMENT IS IGNORED
%CBLCNVRT GLOSTAB COBOL II13
Same errors as II12
In hlq.PANAUDIT.PLUS30C.PANLIB I found
-------------
NAME
CBLSII
CBLSII1X
CBLSII12
CBLSII13
-------------
Do I need to contact our system support people for a new library for Easytrieve? |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19243
Location: Inside the Matrix
|
|
|
|
Hello,
| Quote: |
| Do I need to contact our system support people for a new library for Easytrieve? |
Yes. The library i use for CBLCNVRT has these CBLSx members:
CBLSII
CBLSII12
CBLSII13
CBLSI122
CBLSI212
CBLSI320
CBLSI341
CBLSRCII
CBLSRCVS
CBLSVS |
|
| Back to top |
|
|
Douglas Wilder
Active User
Joined: 28 Nov 2006
Posts: 305
Location: Deerfield IL
|
|
|
|
Now that system support have put macros cbldi341, cblii341 and cblsi341 in the panvelette library I am back to the original error.
We believe that the error is caused by the following line in macro CBLCNVRT. Others of you that have this working, does this line look any different?
| Code: |
| 000083 FILE FIELDS F (462) VIRTUAL RETAIN |
|
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19243
Location: Inside the Matrix
|
|
|
|
Hello,
| Quote: |
| Now that system support have put macros cbldi341, cblii341 and cblsi341 in the panvelette library |
If this is all that was done, you probably have macros that are out of sync. . .
The whole set of cblcnvrt macros needs to be consistent. These are not meant to "mix and match" between sets/releases.
What i did was to create a separate macro library for cblcnvrt and put all of the current set in that library. |
|
| Back to top |
|
|
Douglas Wilder
Active User
Joined: 28 Nov 2006
Posts: 305
Location: Deerfield IL
|
|
|
|
I agree, but I am not in charge of system support nor do I have contact with CA support, nor do they tell me exactly what they do.
Are you in system support? Where did you get the macros in order to “put all of the current set in that library”? Did you also get this error? Is that how you knew to do this? Is it unreasonable for me to expect system support to do this, if this is what is needed to make it work? If I had these macros and put them in a separate macro library it would only fix the problem for me, not the rest of the Easytrieve users on the system.
I do not expect you to be able to give me the up to date macros nor tell me the changes I need to make in order for my macros match the up to date, but could you tell me how this one line should read? |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19243
Location: Inside the Matrix
|
|
|
|
Hello,
| Quote: |
| but I am not in charge of system support nor do I have contact with CA support |
Understood, but someone is. . . And they need to work with CA support.
The statement you asked about "FILE FIELDS" is at line 160 (rather than 83) in the set i use that works and the code is not exactly the same. . . It sounds like your set of macros is closer to an old set of macros i found on a system here (that do not work). The "FILE FIELDS" is at line 83 in those macros that don't work.
As an experiment, i compared my "old" macro that has the FILE FIELDS at line 83 with the one that works and this is the output stats from the compare:
| Code: |
2409 NUMBER OF LINE MATCHES 358 TOTAL CHANGES (PAIRE
16 REFORMATTED LINES 57 PAIRED CHANGES (REFM
332 NEW FILE LINE INSERTIONS 291 NON-PAIRED INSERTS
51 OLD FILE LINE DELETIONS 10 NON-PAIRED DELETES
2757 NEW FILE LINES PROCESSED
2476 OLD FILE LINES PROCESSED
|
As you can see, there are many differences - not just that one statement.
Someone in your support group really needs to get the current macro library from CA. . . (IMHO). This can be done without any other product changes as these macros are external to the Easytrieve install (or should be). Possibly you can get permission to open an issue with CA to get the new macro library. Or, Possibly your manager can provide some assistance if the value of having this working is understood. |
|
| Back to top |
|
|
Douglas Wilder
Active User
Joined: 28 Nov 2006
Posts: 305
Location: Deerfield IL
|
|
|
|
| Thank you. Our CBLCNVRT also has 2476 lines. I have notified System Support that we really need the new version of this macro also. I sure hope that they are working with CA Support, but this does make me wonder about it. |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19243
Location: Inside the Matrix
|
|
|
|
Hello,
To repeat. . .
In order to isolate this from impacting the several hundred developers/users who run Easytrieve, i build a separate maclib for this. It is only used for CBLVNVRT processing. |
|
| Back to top |
|
|
Douglas Wilder
Active User
Joined: 28 Nov 2006
Posts: 305
Location: Deerfield IL
|
|
|
|
| I will pass your recommendation on to our System Support, but since this is "only used for CBLCNVRT processing", and what is in the production macro library now does not work, what harm would be done to upgrade just the CBLCNVRT related macros in the library where all Easytrieve developers/users would expect to find them instead of putting them in some other library no one else has heard of? |
|
| Back to top |
|
|
Douglas Wilder
Active User
Joined: 28 Nov 2006
Posts: 305
Location: Deerfield IL
|
|
|
|
| Note: We are testing it in a separate library, but it seems to me to be a full copy of the production Easytrieve Macro Library. Are you saying once this works we should remove these macros from the normal production Easytrieve macro library and store them in a separate macro library? |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19243
Location: Inside the Matrix
|
|
|
|
Hi Douglas,
| Quote: |
| what harm would be done to upgrade just the CBLCNVRT related macros in the library where all Easytrieve developers/users would expect to find them |
I didn't know what risk there might be, and so i isolated these. Everyone else uses the standard macro library.
This library is only the macros used by CBLCNVRT. So far, i'm the only one here who has ever used CBLCNVRT (no one even knew about this feature until i got here, tried to use it, and discovered that it was "broke".
The Easytrieve in use here is also an old release. I'm hoping the system support people will upgrade to the current release later this spring or summer and that should do away of the need for this extra maclib. |
|
| Back to top |
|
|
Douglas Wilder
Active User
Joined: 28 Nov 2006
Posts: 305
Location: Deerfield IL
|
|
|
|
I now have my own library with the CBLCNVRT macros like you.
As in your case I'm hoping the system support people will upgrade later and do away with the need for this extra macro library. I learned of CBLCNVRT on this forum and introduced it here, before that no one here had heard of it either.
On another note: I did not care for the way the variable definitions took 2 lines each when they did not need to so I threw together the following easytrieve to combine lines. I did very limited testing so far. I thought others might like it. Let me know if you find improvement to make to it.
Thank You for all of your help.
| Code: |
| Code removed per request. |
|
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19243
Location: Inside the Matrix
|
|
|
|
Hi Douglas,
| Quote: |
| Thank You for all of your help. |
You're most welcome
| Quote: |
| I did not care for the way the variable definitions took 2 lines each when they did not need |
Yup, i don't like that either - just haven't done anything about it 
Thanks for posting your code - i'll try a few runs early next week (i'll be away from a connection most of the weekend and Monday).
d |
|
| Back to top |
|
|
|
|
