|
View previous topic :: View next topic
|
| Author |
Message |
rchandran_19
New User
Joined: 08 Mar 2005
Posts: 34
|
|
|
|
Hi,
I am working on a Bull Mainframe System. All programs are in COBOL 74.
Having problem trying to figure out why when you do a rollback, the system is rolling back even the SYSOUT. Is there a way to save some information somewhere, so that in an event a rollback occurs to the last checkpoint, we can get the reason for the abort?
If my question is not clear, let me give a simple example and explain...for eg: a program reads from an input file and writes to an output file. After reading 100 records, and say it has written 10 rec to the output. Now it takes a checkpoint. It continues to read further down the input file....and after reading say another 50 rec, something happened (eg: SOC7) and the system would now execute the rollback subroutine and rolls back to the last checkpoint, ie, rec no 100 of the input file and rec 10 on the output file. up to this point everything is working fine. But before an abort (or rollback), I am displaying some messages like, last record read etc...for debugging. But the rollback has even rolled the sysout. I checked in the WRAPUP and dump and the display statement are no where present.
Is there a way around this problem?
Thanks,
RC |
|
| Back to top |
|
 |
bhairon singh rathore
New User
Joined: 19 Jun 2008
Posts: 91
Location: banglore
|
|
|
|
Please check with your peers regarding the same because it would be site specific  |
|
| Back to top |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006
Posts: 6250
Location: Mumbai, India
|
|
|
|
1. What does "Bull" signifies in "Bull Mainframe System"?
2. Check-point restart logic is limited to the input/output files you work with; that has nothing to do with SYSOUT datasets. How do you conclude SYSOUT is wiped off? Just a guess, are you using correct MSGCLASS? |
|
| Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10873
Location: italy
|
|
| Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10873
Location: italy
|
|
|
|
that was the smartness of some old time operating systems...
even if zOS thinks otherwise,
SYSOUT rollback is a great thing, and also rollback for sequential datasets
no need to write the sysout in a db2 table and print it in a later step |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
| Quote: |
| Check-point restart logic is limited to the input/output files you work with; that has nothing to do with SYSOUT datasets. |
Not all operating systems have the same limitations. . . It can be SYSOUTs as well as other non-database data. . . |
|
| Back to top |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006
Posts: 6250
Location: Mumbai, India
|
|
|
|
Thank you Enrico. Links provided a good information -- not sure what I missed while googling on "Bull"...Thanks again.
Links are saved in Favorites/Other Mainframes Providers...  |
|
| Back to top |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006
Posts: 6250
Location: Mumbai, India
|
|
|
|
Hi Dick,
Now that's the advantage of working with elder goldies... . You, being young, just drift a bit and you got at least two helping hands, Thanks.
Thank you both.
RC -- please ignore my first post in this thread...  |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hi Anuj,
| Quote: |
| You, being young, just drift a bit |
Younger than only a few i suspect. . . And i do try not to drift. . .
| Quote: |
| you got at least two helping hands, Thanks. |
Kind words - most appreciated
d |
|
| Back to top |
|
|
|
|
