View previous topic :: View next topic |
Author |
Message |
chandhroo Beginner
Joined: 02 Dec 2002 Posts: 36 Topics: 13
|
Posted: Fri Nov 07, 2003 5:36 am Post subject: Issue with removal of SYS1.COB2LIB with OPTCD. |
|
|
Hi all,
Currently I'm working on the project which is removal of SYS1.COB2LIB making the application to run in LE370. For one program I'm getting abend
ABEND=S000 U0004 REASON=00000000 816. and message from SYSOUT is DISKIA OPEN ERROR - STATUS 90.
Please find the DD card for DISKIA below.
//DISKIA DD DSN=datasetname,DISP=SHR,
// DSORG=DA,OPTCD=RF
Select statement for the above DD:
SELECT G381-TEXT-FILE ASSIGN TO DISKIA
FILE STATUS IS LK-G381-FILE-STATUS.
and FD entry:
FD G381-TEXT-FILE IS EXTERNAL
RECORD CONTAINS 120 CHARACTERS
RECORDING MODE IS F.
During my analysis, I had just changed OPTCD value to R instead of RF, it ran fine. I had gone through description of OPTCD in QW, but couldn't understand difference clearly. Could anyone of you explain me the usage of OPTCD? And I have recommended the OPTCD change from RF to R. Is this the correct recommendation or is there anything else causes the abend. Please let me know if above given information is not sufficient.
Looking forward your suggestion
Thanks
Chandra |
|
Back to top |
|
|
kolusu Site Admin
Joined: 26 Nov 2002 Posts: 12376 Topics: 75 Location: San Jose
|
Posted: Fri Nov 07, 2003 7:16 am Post subject: |
|
|
chandhroo,
I am very interested to know that cobol supports DA(Direct Access). DA is associated with BDAM (Basic Direct Access Method) and BDAM is no longer supported by IBM.
You have to allocate a RRDS (VSAM) file and repro your file to the VSAM file. Use the new RRDS file in your run JCL.
Another option is to copy the BDAM file to a QSAM file using IEBGENER. Make sure that IEBGENER is running the program IEBGENER instead of locally installed sort product as sort products does not support dsorg=da
Hope this helps...
cheers
kolusu |
|
Back to top |
|
|
Mervyn Moderator
Joined: 02 Dec 2002 Posts: 415 Topics: 6 Location: Hove, England
|
Posted: Fri Nov 07, 2003 5:16 pm Post subject: |
|
|
Quote: |
I am very interested to know that cobol supports DA(Direct Access). DA is associated with BDAM (Basic Direct Access Method) and BDAM is no longer supported by IBM.
|
Interesting. Our Librarian datasets are all DA. As a matter of fact, I was under the impression that BDAM (aka BSAM) was the fundamental building block from which all other access methods have developed, and RRDS is a very simple extension.
Comments, anyone? _________________ The day you stop learning the dinosaur becomes extinct |
|
Back to top |
|
|
slade Intermediate
Joined: 07 Feb 2003 Posts: 266 Topics: 1 Location: Edison, NJ USA
|
Posted: Sun Nov 09, 2003 2:00 pm Post subject: |
|
|
Hi Chandra,
Do other pgms use this file? Do any use it in direct access mode? Are there any other DA files in your shop?
The reason for these ques is that I notice you define the file as sequential which precludes its use in the pgm as a direct access file.
You may want to analyze the pgm with a view toward converting the file as Kolusu suggests. If this is the only pgm using the file, file conversion may be a good idea. If there are other BDAM files extant in the same situation, they may be candidates for similar handeling.
Regards, Jack. |
|
Back to top |
|
|
slade Intermediate
Joined: 07 Feb 2003 Posts: 266 Topics: 1 Location: Edison, NJ USA
|
Posted: Mon Nov 10, 2003 1:28 am Post subject: |
|
|
Hi Chandra,
Do other pgms use this file? Do any use it in direct access mode? Are there any other DA files in your shop?
The reason for these ques is that I notice you define the file as sequential which precludes its use in the pgm as a direct access file.
You may want to analyze the pgm with a view toward converting the file as Kolusu suggests. If this is the only pgm using the file, file conversion may be a good idea. If there are other BDAM files extant in the same situation, they may be candidates for similar handeling.
Regards, Jack. |
|
Back to top |
|
|
chandhroo Beginner
Joined: 02 Dec 2002 Posts: 36 Topics: 13
|
Posted: Mon Nov 10, 2003 11:40 am Post subject: |
|
|
Kolusu/Slade,
Sorry for the delayed response. Actually physical file for DISKIA is sequential file not BDAM, which is used in other jobs as well. However in the JCL it is coded as
DSORG=DA,OPTCD=RF which make us to think as BDAM. I don't know the reason behind coding this for sequential file. It runs well if we concatinate SYS1.COB2LIB in STEPLIB and abends if we remove this dataset.
For testing I had taken out DSORG=DA,OPTCD=RF parameters from DISKIA DD card which runs successfully without abend. I think these two parameters are not necessary. Please suggest me.
--Chandru |
|
Back to top |
|
|
slade Intermediate
Joined: 07 Feb 2003 Posts: 266 Topics: 1 Location: Edison, NJ USA
|
Posted: Tue Nov 11, 2003 12:46 am Post subject: |
|
|
Hi Chandru,
Have you looked at the code to verify that the file is processed as a seq file? If there is no key manipulation or anticipation of a key in the code it is probably safe to assume a seq file.
Have you done a LISTCAT against the file? How does it define the file?
How is the pgm coded to handle file status return codes? The OPTCD F seems to indicate a specific file status presentation request. You may want to force some file status situtations to verify that the removal of the 2 JCL sub params does not change file status processing.
Have you looked at the other pgms? How do they handle the OPTCD? How about the pgm that creates the file? Are there any updates to the file? How are they done? If there are no surprises here, you may want to proceed as follows:
If the pgm executes as expected under these special file status circumstances, and other testing validates the changes, I'd move them into production and watch it closely for a while.
You can't keep that COBOL2 run time library around forever. Eventually it'll bite you.
Regards, Jack. |
|
Back to top |
|
|
chandhroo Beginner
Joined: 02 Dec 2002 Posts: 36 Topics: 13
|
Posted: Tue Nov 11, 2003 6:18 am Post subject: |
|
|
Jack,
1. That file contains text message which doesn't have any key field and it is being read in way sequential read.
2. Please find LISTCAT result:
THE NUMBER OF ENTRIES PROCESSED WAS:
AIX -------------------0
ALIAS -----------------0
CLUSTER ---------------0
DATA ------------------0
GDG -------------------0
INDEX -----------------0
NONVSAM ---------------1
PAGESPACE -------------0
PATH ------------------0
SPACE -----------------0
USERCATALOG -----------0
TAPELIBRARY -----------0
TAPEVOLUME ------------0
TOTAL -----------------1
THE NUMBER OF PROTECTED ENTRIES SUPPRESSED WAS 0
IDC0001I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 0
3. File status is being handled as follows:
READ G381-TEXT-FILE INTO G381-TEXT (TEXT-CTR).
IF LK-G381-FILE-STATUS = '10'
GO TO READ-G381-TABLE-EXIT.
IF LK-G381-FILE-STATUS NOT = '00'
DISPLAY 'S2010 - DISKIA READ ERROR - STATUS '
LK-G381-FILE-STATUS
DISPLAY 'RECORD NUMBER - ' TEXT-CTR
ADD 1 TO LK-G381-ERROR
MOVE 'Y' TO LK-FORCE-ABEND-SW
GO TO P-END-MODULE.
ADD 1 TO LK-G381-READ-CTR.
READ G381-TEXT-FILE INTO G381-TEXT (TEXT-CTR).
IF LK-G381-FILE-STATUS = '10'
GO TO READ-G381-TABLE-EXIT.
IF LK-G381-FILE-STATUS NOT = '00'
DISPLAY 'S2010 - DISKIA READ ERROR - STATUS '
LK-G381-FILE-STATUS
DISPLAY 'RECORD NUMBER - ' TEXT-CTR
ADD 1 TO LK-G381-ERROR
MOVE 'Y' TO LK-FORCE-ABEND-SW
GO TO P-END-MODULE.
ADD 1 TO LK-G381-READ-CTR.
4. In my application OPTCD has been used only for two programs. One is this one used for sequential file, other is used for BDAM file which is being read by Assembler program so, it doesn't create any problem.
5. And this file is neither being created nor updated by any other program, this is just kind of text file used for linkage referencing. Only this job uses this file.
Now im thinking to to take out both DSORG and OPTCD parameters from the DD card to move to production making it successful. Pass your feedback.
Thanks
Chandru |
|
Back to top |
|
|
slade Intermediate
Joined: 07 Feb 2003 Posts: 266 Topics: 1 Location: Edison, NJ USA
|
Posted: Wed Nov 12, 2003 12:14 am Post subject: |
|
|
Hi Chandru,
Quote: |
Now im thinking to to take out both DSORG and OPTCD parameters from the DD card to move to production making it successful. Pass your feedback.
|
That was what I was suggesting in my last post. The only thing I would advise is to test the file status processing with and without the DSORG and OPTCD sub params of the DCB. It seems the pgm processes the file OK when no problems are present, but how will it handle error conditions?
For example, use a file with an LRECL that differs from the FD LRECL. Create an empty file with IEFBR14 and input it to the pgm. These should give you error conditions when the file is OPENed. See if you get identical results from the before annd after versions of the pgm in each case. If you do get identical results, the odds are good that the changes you made are valid.
If it were me I'd run those 2 tests before I moved the pgm to production.
Good luck, Jack. |
|
Back to top |
|
|
chandhroo Beginner
Joined: 02 Dec 2002 Posts: 36 Topics: 13
|
Posted: Thu Nov 20, 2003 3:30 am Post subject: |
|
|
Jack,
Sorry I was not able to connect internet for a week, that's why I couldn't respond. Actually now I have taken out both DSORG and OPTCD. I have also tested with empty and different LRECL file. New version JCL performs as Base version. Thanks a million for your valuable time.
Regards
Chandru |
|
Back to top |
|
|
slade Intermediate
Joined: 07 Feb 2003 Posts: 266 Topics: 1 Location: Edison, NJ USA
|
Posted: Fri Nov 21, 2003 9:55 pm Post subject: |
|
|
Hi Chandru,
Thanx for taking the time to let us know how you got past your problem. It helps everyone in the Forum to know what worked and what didn't.
Regards, Jack. |
|
Back to top |
|
|
|
|