Common VMCF problems

The following problems are some common VMCF problems:

• VMCF or TNF fail to initialize with an 0C4 abend.

  This is probably an installation problem; check the program properties table (PPT) entries for errors. Some levels of MVS™ do not flag PPT syntax errors properly.

• Abends 0D5 and 0D6 after REMOVEing a user.

  This is probably because the application is still running and using VMCF. It is not recommended that users be removed from VMCF or TNF without first terminating the affected user.

• VMCF or TNF do not respond to commands.

  This is probably because one or both of the non-restartable versions of VMCF or TNF are still active. To get them to respond to commands, stop all VMCF/TNF users, FORCE ARM VMCF and TNF, then use EZAZSSI to restart.

• VMCF or TNF cannot be stopped.

  This is probably because users still exist in the VMCF and TNF lists. Use the F VMCF,DISPLAY,NAME=* and F TNF,DISPLAY,NAME=* commands to identify those users who are still active. Then either cancel those users or remove them from the lists using the F VMCF,REMOVE and F TNF,REMOVE commands.

• Address Space Identifiers (ASIDs) become nonreusable when VMCF and TNF address spaces are stopped or restarted.

  Because VMCF and TNF address spaces provide PC-entered services that must be accessible to all address spaces, they each obtain a system LX. This causes the ASIDs associated with these address spaces to be nonreusable when these address spaces are terminated. If VMCF and TNF are terminated enough times all available ASIDs could be exhausted, preventing the creation of new address spaces on the system. In this case, an IPL will be required. For more information on tuning parameters for the maximum number of ASIDs in a system, see the MAXUSER parameter in z/OS MVS Initialization and Tuning Reference.