Discussion created by ca.portal.admin on Jul 16, 2010
My memory may be getting creaky, but I don't believe this is a stand-alone
program. I believe it was used to do sequential I/O to utility files (like
backups and tape journals). Sort of an IDMBDBIO but for sequential files.
Linked/loaded by the various routines that needed it.

Don Casey
Principal Consultant
Run Right, LLC

----- Original Message -----
From: William M. Allen, Jr. <archcons@ARCHCONS.COM>
Sent: Fri, 16 Jul 2010 16:18:01 -0000 (UTC)

Anyone have any OLD documentation on the IDMSUTIO program? I can't find
anything in and release 12,14,15,16 or 17 manuals that gives any details.

William M. Allen, Jr.

ARCH Consulting Associates, Ltd.

(704) 641-0296
IDMS 3rd-party providers forum



z/VSE and z/OS both process sequential and BDAM files in semantically
similar ways but use different macros to accomplish the task. Calls to
IDMSUTIO can be used to open, read, write and close files eliminating the
need to maintain different source modules for different operating systems.
UTIO uses different code paths to perform IO depending on your environment
so you don't have to.

Unless you need to a single source program to run on both operating systems
(like you might do in a software product), you should consider replacing the
calls with more traditional facilities, i.e. COBOL file processing verbs...

With that said, we just went through this during the port of our XMLQuery
product to VSE. I think the CAS documentation has some notes on using UTIO.
We don't have that documentation but perhaps someone out there can dig it
out. If you have access to CAS source code you will find IDMSUTIO being
used in many of its COBOL batch programs. They would make good samples. We
managed to find some old application code and used it as sample. UTIO must
be statically linked which is a bit annoying so we are contemplating writing
our own similar program to be dynamic and reentrant. If you don't find more
information, send a note offline and we'll send you a sample.

Perhaps CA can post a docup on their support site. Remember if it's not
documented CA could change specs or even remove it from their product
without notice. I suspect that would be pretty unlikely but it could become
an issue in some future release.