z/VM Module 5: Advanced Structures and Commands

1. z/VMModule 5: Advanced Structures and Commands Control Program

2. Objectives • List and describe additional CP commands, including: • Privilege classes • Command descriptions • Syntax diagrams • Usage notes • List and describe useful CP utilities, including: • Descriptions • Functions • Usage notes

3. Advanced CP Commands

4. DETACH • Use the DETACH commands to detach the following: • Virtual processors from your virtual machine • Real devices from the host system • Logical devices from the host system • Real devices from your virtual machine • Logical devices from your virtual machine • Virtual devices from your virtual machine • A Virtual Vector Facility from your virtual machine • And more

5. DETACH Usage Notes • These are some of the CP DETACH commands: • DETACH CFLINK • DETACH CPU • DETACH CRYPTO • DETACH LAN • DETACH NIC • DETACH MSGPROC • DETACH (Real Device) • DETACH VECTOR • DETACH (Virtual Device) • DETACH XSTORE • You can find more information in the CP Command and Utilities Reference and in z/VM’s help facility:

6. TERMINAL

7. TERMINAL Usage Notes • You can specify more than one function in a single entry of the terminal command • For CHARDEL, LINEND, TABCAR, and ESCAPE you cannot use any letter A through Z, the numbers 0 through 9, or the bytes X’0E’ or X’0F’ as a symbol • The system operator can specify system defaults for the TERMINAL LINEND, CHARDEL, TABCHAR, and ESCAPE characters • The characters displayed depend on the code page used by the terminal emulator

8. SET • The SET command is used interchangeably within CP and CMS to control commands • It controls such functions as:

9. INDICATE USER

10. INDICATE USER Usage Notes • Use this command to display the total amount of resources used by your virtual machine during your current session. • Use it before and after the execution of a program to determine the execution characteristics of that program. • If the expanded response is given for a user who is logging on or off and does not have a base address space, then the primary space name and space type will be filled with “*” in the response.

11. INDICATE USER Responses

12. INDICATE USER Responses continued

13. INDICATE USER Responses continued

14. CP Utilities

15. DIRECTXA Utility

16. How the Directory Program Works • If a file name or type is not specified, then the file name is USER with a file type of DIRECT (defaults) • If any type of error occurs the program does not create the directory • This utility looks up and uses the RPWLIST DATA file, which contains a list of restricted passwords • If DIRECTXA runs out of DASD space, the utility issues an error message, and the directory is not processed • If the program is updating an active system directory, the program makes the new directory immediately available for the system

17. DIRECTXA Utility Usage Notes • To update the system user directory, you must be of privilege class A, B, or C. • If another user directory exists, the DIRECTXA utility does not overwrite the current directory, but does write an alternate user directory. • If the directory specified on the DIRECTXA utility is not the current directory, the directory that is created by this utility is not brought online. • The MIXED option should be used during migration from other releases.

18. DIRECTXA Utility Examples • Listed below are different examples of altering or creating the user directory: • Directxa user direct * • Directxa user direct * (edit mixed • Directxa user direct *(edit mixed mixmsg sysafnid sysyma • Directxa user direct * (edit sysafnid sysyma • Directxa user direct * (mixed nomixmsg

19. DISKMAP Utility

20. DISKMAP Utility Usage Notes • Some DASD types come in several sizes, so the end gap is not listed. • DISKMAP creates the map on your A-disk, so you may need to clear space if your A-disk might fill up. • You may want to lay out your MDISK design first to distinguish between overlap errors or plan overlaps. • If you want end statements to display the end of each MDISK you must issue the DOENDS operand.

21. CPFMTXA Utility

22. CPFMTXA Utility Operands

23. Changing the Allocation Map • An allocation map of the disk is displayed to verify that it is the correct disk and that you are sure changes are needed. • Within your allocation map you can define a directory, page space, spool space, temporary disk space, etc. • You must always define the cylinder range and total number of cylinders that are to be allocated for each defined space

24. Changing the Allocation Map continued

25. Interactions with ICKDSF • The example in the notes shows the prompts that are issued if ICKDSF is available and you enter CPFMTXA only. • If you entered: • cpfmtxa y • you will be prompted to format, allocate, or label the DASD you specify. • If you format the entire DASD you may have to wait several minutes for it to complete formatting.

26. Interactions with ICKDSF continued • This continuation demonstrates what happens when you specify space for spooling, temporary disk, perm (static space), and page (paging space). • Below is an example of what you could allocate and the different ways you can represent it: • TYPE CYLINDERS • .................. • perm 0.3 • spol 3.300 • tdsk 303 450 • page 451-500 • perm 501-end • end

27. CPFMTXA Utility Usage Notes • If ICKDSF is not on an accessed disk no formatting, allocating, or labeling will occur. • Before using the ALLOCATE option you must format the volume. • CPFMTXA will prompt you many times during a format operation to confirm that you want to continue, since formatting the disk will erase all data on the disk • There are three different ways to specify the cylinders to be formatted: • cpfmtxa 192 test1 • cpfmtxa 192 test2 0.3 • cpfmtxa 192 test3 0-3

28. CPFMTXA Utility Usage Notes continued • DRCT, PAGE, PARM, PERM, SPOL, and TDISK are allocation types. • If the allocation record is overwritten, it is effectively destroying any pointer to the active directory and rending it inaccessible. • Space for system dumps and system data files needs to be allocated as SPOL space. • ICKDSF reserves pages 0-3 for system use.

29. Conclusion • CP commands you should understand and be able to use: • DETACH • TERMINAL • SET • INDICATE USER • CP utilities that you should understand and be able to use: • DIRECTXA • DISKMAP • CPFMTXA • The first five modules cover the fundamentals of the z/VM environment

30. Glossary • CPFMTXA – can be used to ESA format, label, and allocate DASD volumes for CP uses such as paging, spooling, temporary disk, directory, nucleus, and minidisk space. • DETACH –detaches attached devices owned by the current user. • DIRECTXA – creates a user directory. • DISKMAP – summarizes the minidisk statements in the user directory.

31. Glossary • INDICATE USER – displays the resources used and occupied by a virtual machine or by the system. • SET –describes the various functions associated with your virtual machine or with the z/VM system. • TERMINAL –controls various characteristics of your virtual console.