iSeries languages, utilities, and licensed programs
The iSeries™ languages, utilities, and licensed programs in this topic can access remote CICS® files.
- Programs written in the following languages on an iSeries server can access remote CICS files:
- ILE C programming language
- See ILE C considerations.
- CL
- See iSeries CL considerations.
- ILE COBOL programming language
- See ILE COBOL considerations.
- See PL/I considerations.
- ILE RPG programming language
- See ILE RPG considerations.
- Programs written in BASIC might cause results that cannot be predicted when accessing remote CICS files.
- iSeries Query can access the remote entry sequence data set (ESDS), relative record data set (RRDS), and key sequence data set (KSDS). However, iSeries Query cannot access virtual storage access method (VSAM) files through DDM.
- The licensed program iSeries Access Family might cause results that cannot be predicted when accessing remote CICS files.
Some of the high-level languages provide access to the server database I/O feedback area. When accessing a remote VSAM RRDS, this area will contain the relative record number. However, when accessing other types of VSAM data sets, the relative record number is not known and a value of -1 is returned as the relative record number.
Additional considerations might apply when accessing CICS files which are to be read or written by a System/370™ host due to the way a System/370 host stores data. For example, the System/370 host representation of a floating point number is different from the iSeries server representation of a floating point number.
- CRTDDMF (Create DDM File) considerations
For applications running on an iSeries server to access remote files, the programmer must use the CRTDDMF command to create an object called a DDM file.
- iSeries CL considerations
Besides the information in this topic collection, consider these topics when using iSeries CL commands to access VSAM data sets on a remote CICS system.
Parent topic:
iSeries server-to-CICS considerations with DDM