(no subject)

[dkhansen@xxxxxxxx]

My name is Dusty Hansen.  I am a programming manager of 17 programmers.  We are
going to try and go from our current COBOL CICS main frame platform to COBOL/400
on the 400.  We are currently running our batch processing on the 400 but we
need to migrate all of our 800 COBOL programs and 400 BMS maps to the 400.  We
will then have our interactive portion on the 400 and we can get ride of the
bigger main frame.   I have read some very good mail posted in the archives.
This has been very valuable.

I am looking to see if we there is a way that a called program can kill the
calling program and run on it's own?  If you have a stack and the main calling
program calls a sub program which calls others, do we have to keep the
relationship of the main program or can we kill it at some point?  With what we
are doing we do not need the initial calling program once we have transferred
control to one of the sub programs.

In our CICS world we have a display program that reads a record and then sends a
map to the screen.  The display program then goes away.  If there has been any
thing coded on the screen the update program is invoked and reads the map,
updates the record and then send out the output map (screen).  the update
program then goes away.  This is handled by using the CICS XCTL command.  This
will transfer control to another program and then go away.  Is there an
equivalent situation for COBOL/400?