Loading and Running under z/VM

Before you can run a program under z/VM, you must issue one of the following commands:

• LOAD (Stores a copy of the program in virtual storage)
• GENMOD (Stores the program on disk)
• LKED (Stores the program in a LOADLIB)
• BIND (Stores the program on disk using the Program Management binder)

z/VM produces an object module with the file type TEXT when you compile your program. Before you run the program, external references inserted by the compiler must be resolved. Use one of the following methods to create an executable application; you can run your application after you complete any of these steps.

• Create a temporary copy of your program in virtual storage by using LOAD and INCLUDE commands. No permanent copy of the executable program is made.
• Create a module using LOAD, INCLUDE, GENMOD, and/or BIND commands if appropriate. A module is an executable application that is stored as a file with a file type of MODULE.
• Create a module in a member of a library using the LKED command. This method link-edits an executable application and stores it as a load module in a member of a CMS LOADLIB.
• Create a module using the CMOD EXEC (C applications only). See Using the CMOD EXEC for more information.

Restrictions:

• VisualAge® PL/I and Enterprise PL/I are not supported on z/VM. Language Environment continues to provide support for PL/I applications under z/VM compiled with PL/I for MVS & VM, and previous, supported levels of the PL/I compiler.
• Language Environment does not support Fortran applications in the z/VM environment.
• Enterprise COBOL for z/OS and z/VM.
• COBOL programs compiled with the DLL or ARITH(EXTEND) compiler options are not supported on z/VM.
• COBOL programs using object oriented constructs, LINE SEQUENTIAL files, or dynamic allocation using environment variables are not supported on z/VM.
• COBOL multi-threaded or multi-tasking programs are not supported on z/VM.