× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.




Thanks for the information.  We converted our batch system to the 400 a few
years ago.  It was a very straight forward move.  We had been running RPGII.  It
was very easy to convert the RPGII to RPG400.  The biggest part was converting
all of the JCL to CLs and CLPs on the 400.  It is pretty easy and there are
equivalents to most of the JCL commands.   We use sorts in our CLs as we are
still on a flat file system and have not developed our data base yet.  There was
a tremendous increase in productivity once we had moved our batch to the 400.

Thanks!
Dusty Hansen
801-233-3248
dkhansen@fbfs.com





"Mark Villa" <markvilla@knology.net> on 01/01/2002 01:17:43 PM

Please respond to cobol400-l@midrange.com

To:   cobol400-l@midrange.com
cc:    (bcc: Dusty Hansen/UT/FBFS)

Subject:  RE: Converting from CICS (was no subject)



~~~I would like to tell you that we have implemented CICS/400
~~~for the VSE/CICS
~~~programs/applications.  IT SCREAMS ... when we started, we

Awesome task list! Would love to have been involved in this from a learning
perspective.

Curious, how many people does it take for six months? or how to judge the
man-hours if it ever comes up?

I understand the challenge of the CICS conversion, and believe that baby has
be near perfect, but the job streams for batch would seem to be the real
challenge.

It is also EASY to see mentally how CICS/400 would scream past a VSE box
with current hardware.

I had often thought what I would do if fell into this conversion. I had
thought of using the System/36 environment type coding on the AS/400 for
batch processes, if it was an emergency rush job type thing, as a stepping
stone to ILE. It also lets you break all the rules like VSE Cobol.
The S/36 Cobol and OCL is the closest thing to JCL using VSAM I've seen. I
would think it was strikingly similar if IBM was not the vendor for both.
It's almost a one to one relationship between OCL, sorts, Cobol not
initializing working storage, etc.

Very interesting notes. Thanks for sharing it!

Mark Villa in Charleston SC

_______________________________________________
This is the COBOL Programming on the iSeries/AS400 (COBOL400-L) mailing list
To post a message email: COBOL400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/cobol400-l
or email: COBOL400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/cobol400-l.









As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.