Skip to ContentSkip to Footer
Start of content
- Community Home
- >
- Servers and Operating Systems
- >
- Operating System - OpenVMS
- >
- COBOL Objects with IO statements, wrapped by WSIT
Operating System - OpenVMS
-
- Forums
-
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
- HPE Blog, Austria, Germany & Switzerland
- Blog HPE, France
- HPE Blog, Italy
- HPE Blog, Japan
- HPE Blog, Middle East
- HPE Blog, Latin America
- HPE Blog, Russia
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
-
Blogs
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Blog, Latin America
- HPE Blog, Middle East
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
-
Information
- Community
- Welcome
- Getting Started
- FAQ
- Ranking Overview
- Rules of Participation
- Tips and Tricks
- Resources
- Announcements
- Email us
- Feedback
- Information Libraries
- Integrated Systems
- Networking
- Servers
- Storage
- Other HPE Sites
- Support Center
- Aruba Airheads Community
- Enterprise.nxt
- HPE Dev Community
- Cloud28+ Community
- Marketplace
-
Forums
-
Blogs
-
Information
-
English
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
02-07-2008 09:05 AM
02-07-2008 09:05 AM
Re: COBOL Objects with IO statements, wrapped by WSIT
Maurizio, Those rules 1 & 2 I posted earlier were direct quotes from the manual.
This is how it is, and how it is intended to be, so it is how it stays. This may still be relevant for your problem.
I do not have much handson experience with this, I just know several
folks were surprised by this behaviour over time.
$ help cobol proc exit
$ help cobol proc stop
I guess I would make sure to put some printout and/or lib$signal and/or sys$exit calls between a suspect 'exit program' and the next paragraph.
Hmmm, which reminds me, did you try with a compile /STANDARD=V3?
From an old (1997) note:
V2.4-919 A problem has been corrected which involved the use of the
EXIT PROGRAM statement in a local USE procedure of a COBOL main
program which was compiled with the qualifier /STANDARD=V3.
The problem was that such an EXIT PROGRAM statement did not cause the
execution of the run-unit to terminate immediately, as it does in VAX
COBOL. Instead, the EXIT PROGRAM statement was causing the execution
of the run-unit to continue by returning immediately to the main-line
code of the main program.
Good luck!
Hein.
This is how it is, and how it is intended to be, so it is how it stays. This may still be relevant for your problem.
I do not have much handson experience with this, I just know several
folks were surprised by this behaviour over time.
$ help cobol proc exit
$ help cobol proc stop
I guess I would make sure to put some printout and/or lib$signal and/or sys$exit calls between a suspect 'exit program' and the next paragraph.
Hmmm, which reminds me, did you try with a compile /STANDARD=V3?
From an old (1997) note:
V2.4-919 A problem has been corrected which involved the use of the
EXIT PROGRAM statement in a local USE procedure of a COBOL main
program which was compiled with the qualifier /STANDARD=V3.
The problem was that such an EXIT PROGRAM statement did not cause the
execution of the run-unit to terminate immediately, as it does in VAX
COBOL. Instead, the EXIT PROGRAM statement was causing the execution
of the run-unit to continue by returning immediately to the main-line
code of the main program.
Good luck!
Hein.
- « Previous
-
- 1
- 2
- Next »
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
End of content
United States
Hewlett Packard Enterprise International
Communities
- Communities
- HPE Blogs and Forum
© Copyright 2021 Hewlett Packard Enterprise Development LP