IBM OS/390 Dos Pl/I, VS Cobol II Migration Considerations, DOS/VS Cobol Migration Considerations

Table 38 on page 356 lists some migration considerations you should be aware of when migrating from VS COBOL II.

Table 38. VS COBOL II Migration Considerations

Migration Consideration	Comments
Abends	In VS COBOL II, a severe unhandled error condition
	always resulted in an abend. With OS/390 Language
	Environment, you use the ABTERMENC run-time option
	to specify whether a severe unhandled condition
	results in an abend or a normal termination with a
	return code and reason code. The IBM-supplied
	installation value for the ABTERMENC run-time option
	is ABTERMENC(RETCODE). To ensure that your
	application ends with an abend when there is a severe
	unhandled condition, specify ABTERMENC(ABEND).
Storage Report	The format of the run-time storage report generated
	by the OS/390 Language Environment RPTSTG
	run-time option is different from the format of the
	storage reports produced by the VS COBOL II SPOUT
	run-time option.

17.4.4 DOS/VS COBOL

DOS/VS COBOL is not an LE/VSE-conforming language. If your applications are written in DOS/VS COBOL, you must update the source and compile with COBOL for MVS & VM or COBOL for OS/390 & VM before you can run them under OS/390. Refer to Chapter 12, ªCOBOLº on page249 for further information.

Table 39 lists some migration considerations you should be aware of when migrating from DOS/VS COBOL.

Table 39. DOS/VS COBOL Migration Considerations

Migration Consideration	Comments
Abends	In DOS/VS COBOL, a severe unhandled error condition
	always resulted in an abend. With OS/390 Language
	Environment, you use the ABTERMENC run-time option
	to specify whether a severe unhandled condition
	results in an abend or a normal termination with a
	return code and reason code. The IBM-supplied
	installation value for the ABTERMENC run-time option
	is ABTERMENC(RETCODE). To ensure that your
	application ends with an abend when there is a severe
	unhandled condition, specify ABTERMENC(ABEND).

17.4.5 DOS PL/I

DOS PL/I is not an LE/VSE-conforming language. If your applications are written in DOS PL/I, you must update the source and compile with PL/I for MVS & VM before you can run them under OS/390. Refer to Chapter 15, ªPL/Iº on page 333 for further information.

Table 40 on page 357 lists some migration considerations you should be aware of when migrating from DOS PL/I.

356VSE to OS/390 Migration Workbook