Thanks,
Jeff Buening
Programmer/Analyst
jeff.buening@xxxxxxxxxxxxxxxxxxx
Phone: 419-586-8599
FAX #: 419-586-6224
www.celinainsurance.com
From: cobol400-l-request@xxxxxxxxxxxx
To: cobol400-l@xxxxxxxxxxxx
Date: 05/29/2010 01:01 PM
Subject: COBOL400-L Digest, Vol 8, Issue 23
Thanks Jon, from what I was reading and trying seemed to act just like
doing a STOP RUN in what it shuts down/releases, but just wanted to see if
someone else agreed.
Send COBOL400-L mailing list submissions to
cobol400-l@xxxxxxxxxxxx
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.midrange.com/mailman/listinfo/cobol400-l
or, via email, send a message with subject or body 'help' to
cobol400-l-request@xxxxxxxxxxxx
You can reach the person managing the list at
cobol400-l-owner@xxxxxxxxxxxx
When replying, please edit your Subject line so it is more specific
than "Re: Contents of COBOL400-L digest..."
Today's Topics:
1. Re: COBOL400-L Digest, Vol 8, Issue 22 (Jeff Buening)
2. Re: STOP RUN VS RCLACTGRP (name) (Jon Paris)
----------------------------------------------------------------------
message: 1
date: Fri, 28 May 2010 13:19:55 -0400
from: Jeff Buening <JeffBuening@xxxxxxxxxxxxxxxxxxx>
subject: Re: [COBOL400-L] COBOL400-L Digest, Vol 8, Issue 22
MVH,
Not sure what you are trying to tell me. I know if I use
GOBACK in a
subprogram in same activation group as main program the activation group
stays open and so do files. If I use a goback in the main program it would
be like doing a STOP RUN, so not sure what you mean.
I just want to know whether it is a GOBACK or STOP RUN in a main program in
which the activation group will shut down, does that process do the same
thing(closing files, cursors, unlock files, etc....) as RCLACTGRP (name)
"name" being the activation group I want shut down.
As a side question does anyone see any issue with doing a SELECT statement
embedded SQL COBOL and not shutting down the the *SHRRD lock on a file it
creates. I am wondering if later in the SAME JOB (this being a batch job
no other jobs touch files while running) in which a RSTOBJ happens on the
FILE will it error because the lock still on from previous program in SAME
JOB or does that only affect other jobs doing stuff on the file?
Thanks,
Jeff Buening
message: 2
date: Fri, 28 May 2010 15:02:46 +0200
from: <geir.kildal@xxxxxxxxxx>
subject: Re: [COBOL400-L] STOP RUN VS RCLACTGRP (name)
Hi
Maybe you should have a look at the GOBACK statement
Mvh.
Geir.
"Keep it simple!"
If I have a program running in a activation group "name" and I issue a STOP
RUN in that program it shuts down the activation group, releases file
locks, etc.... If I use the RCLACTGRP (name) does this close the same
stuff the STOP RUN would or is there more to the RCLACTGRP in this
scenario? Basically does STOP RUN and RCLACTGRP(name) do the same thing.
Thanks,
Jeff Buening
Programmer/Analyst
------------------------------
message: 2
date: Fri, 28 May 2010 14:58:06 -0400
from: Jon Paris <jon.paris@xxxxxxxxxxxxxx>
subject: Re: [COBOL400-L] STOP RUN VS RCLACTGRP (name)
The two are effectively the same thing.
Jon Paris
www.Partner400.com
www.SystemiDeveloper.com
On May 28, 2010, at 8:05 AM, Jeff Buening wrote:
If I have a program running in a activation group "name" and I issue
a STOP
RUN in that program it shuts down the activation group, releases file
locks, etc.... If I use the RCLACTGRP (name) does this close the same
stuff the STOP RUN would or is there more to the RCLACTGRP in this
scenario? Basically does STOP RUN and RCLACTGRP(name) do the same
thing.
------------------------------
--
This is the COBOL Programming on the iSeries/AS400 (COBOL400-L) digest list
To post a message email: COBOL400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/cobol400-l
or email: COBOL400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/cobol400-l.
End of COBOL400-L Digest, Vol 8, Issue 23
*****************************************
************************************************************************************
This footnote confirms that this email message has been scanned by
PineApp Mail-SeCure for the presence of malicious code, vandals & computer
viruses.
************************************************************************************
midrange.com
