Migrating from 16-bit | Class Library |
This chapter lists differences in the COBOL System Library Routines compared to Object COBOL and Workbench.
For differences between 16-bit and 32-bit, see the chapter Migrating from 16-bit
Routines are listed alphabetically. If a routine isn't mentioned, we believe no change is needed. Subheadings used in each entry are:
Library routine to test the status of a printer.
Object COBOL V3.4 and Workbench V3.4.
Not available. This routine can work only on DOS, and therefore is not implemented in NetExpress. A dummy routine of this name is included which always returns a result indicating the printer is unavailable.
Recode your program. Remove calls to this routine and check the file status after using a WRITE statement to the printer.
Object COBOL V3.4 and Workbench V3.4.
Not available. This routine can work only on DOS, and therefore is not implemented in NetExpress. Calling it will give RTS error 164 ("Run-time subprogram not found").
Windows 95, Windows 98 and Windows NT V4.0 have no facility equivalent to the one that this routine gives access to, so you will need to redesign your application.
Object COBOL V3.4 and Workbench V3.4.
Not available. This routine can work only on DOS, and therefore is not implemented in NetExpress. Calling it will give RTS error 164 ("Run-time subprogram not found").
Windows 95, Windows 98 and Windows NT V4.0 have no facility equivalent to the one that this routine gives access to, so you will need to redesign your application.
Object COBOL V3.4 and Workbench V3.4.
Not available. This routine can work only on DOS, and therefore is not implemented in NetExpress. Calling it will give RTS error 164 ("Run-time subprogram not found").
Windows 95, Windows 98 and Windows NT V4.0 have no facility equivalent to the one that this routine gives access to, so you will need to redesign your application.
Object COBOL V3.4 and Workbench V3.4.
Not available. This routine can work only on DOS, and therefore is not implemented in NetExpress. Calling it will give RTS error 164 ("Run-time subprogram not found").
Windows 95, Windows 98 and Windows NT V4.0 have no facility equivalent to the one that this routine gives access to, so you will need to redesign your application. You may be able to write a C routine or use a Win32API routine to access the port.
Object COBOL V3.4 and Workbench V3.4.
Not available. This routine can work only on DOS, and therefore is not implemented in NetExpress. Calling it will give RTS error 164 ("Run-time subprogram not found").
Windows 95, Windows 98 and Windows NT V4.0 have no facility equivalent to the one that this routine gives access to, so you will need to redesign your application. You may be able to write a C routine or use a Win32API routine to access the port.
Object COBOL V3.4 and Workbench V3.4.
Not available. This routine can work only on DOS, and therefore is not implemented in NetExpress. Calling it will give RTS error 164 ("Run-time subprogram not found").
Windows 95, Windows 98 and Windows NT V4.0 have no facility equivalent to the one that this routine gives access to, so you will need to redesign your application.
Object COBOL V3.4 and Workbench V3.4.
Not available. This routine can work only on DOS, and therefore is not implemented in NetExpress. Calling it will give RTS error 164 ("Run-time subprogram not found").
Windows 95, Windows 98 and Windows NT V4.0 have no facility equivalent to the one that this routine gives access to, so you will need to redesign your application.
Object COBOL V3.4 and Workbench V3.4.
Not available. This routine can work only on DOS, and therefore is not implemented in NetExpress. Calling it will give RTS error 164 ("Run-time subprogram not found").
Windows 95, Windows 98 and Windows NT V4.0 have no facility equivalent to the one that this routine gives access to, so you will need to redesign your application. You may be able to write a C routine or use a Win32API routine to access the port.
Object COBOL V3.4 and Workbench V3.4.
Not available. This routine can work only on DOS, and therefore is not implemented in NetExpress. Calling it will give RTS error 164 ("Run-time subprogram not found").
Windows 95, Windows 98 and Windows NT V4.0 have no facility equivalent to the one that this routine gives access to, so you will need to redesign your application. You may be able to write a C routine or use a Win32API routine to access the port.
Copyright © 1998 Micro Focus Limited. All rights reserved.
This document and the proprietary marks and names
used herein are protected by international law.
Migrating from 16-bit | Class Library |