1. Z/vm Installation Guide
2. Z/vm Program Directories
3. Z/vm Performance

KICKS User's Guide - Installation KICKS A transaction processing system for CMS & TSO Install Notes Every install environment is different, and there is no way to describe exactly what needs to be done to install any product in every environments. The following and sections are thus necessarily generic.

However, since some environments are well known the following pre-install suggestions are provided. They apply to unmodified versions only (fresh standard installs of the subject operating system distribution). TSO -.

TSO -. TSO -. TSO -. CMS -. CMS -. CMS - z/OS These instructions are for use by a normal TSO user to perform an unassisted install of KICKS into his or her own TSO account.

Instructions for systems programmers to install KICKS for general use are. KICKS has been successfully installed on Z/OS 1.4, 1.6, 1.10, and 1.12. I am not aware of any Z/OS system where it does not install and run.

KICKS is available from a number of sites, including the, so download a copy and review and accept the license. Unzip kicks-tso-v1r5m0.zip resulting in a single folder named kicks-tso-v1r5m0. The following files and folders will be within. Kicks-tso-v1r5m0.xmi - an XMIT file you will upload to your system If you aren't familiar with XMI files I recommend the NASPA reprint on the subject. User's Guide - a folder containing this User's Guide. Note - Although a copy of the User's Guide is included in the distribution package you should always use the online version (at ) if possible as it is the most current.

In particular, many installation problems can be resolved by reinstalling using the instructions in the online version! Kicks-license.txt - a text file of the license you agreed to when you downloaded the KICKS package. Readme.txt - a text file with this information, and telling you to go to the User's Guide Installation section to continue the install. Prepare for install:. Review the environment specific instructions for your TSO environment. It may also be useful to look at the instructions for 'similar' TSO environments. KICKS requires a TSO region of at least 4 megs.

It may start in smaller regions, but abends are likely as it opens more VSAM files and/or runs complicated applications. KICKS can be installed using your TSO id, or your TSO prefix, or some fixed literal as a high level qualifier. The default is your TSO id.

Regardless of your choice, the remainder of these install instructions will refer to that choice as USERID. There are two kinds of KICKS files: 'system' and 'user'. The 'system' files are installed as USERID.KICKSSYS.

And the 'user' files are installed as USERID.KICKS. So if your TSO id (or prefix, or literal) is 'JACKSON' the 'system' files will be JACKSON.KICKSSYS and the 'user' files will be JACKSON.KICKS.

KICKS dataset names include a lower level qualifier of V1R5M0 so they will not conflict with dataset names for earlier KICKS installations. Unless you change it, KICKS non-VSAM files will be allocated on non-specific storage volumes. If you want those files installed on specific volumes you will need to modify the installation code to specify those volumes (see step 7).

This preparation step is to decide if non-specific is OK, and if not what volume(s) you want them on. Unless you change it, KICKS VSAM files will be allocated on volume PUB002. Most shops won't have such a volume, or if they do you probably shouldn't allocate on it. You should change the idcams DEFINE's for these files to specify volumes appropriate to your shop, possibly non-specific, ie, VOLUME(.). See steps 10-14. This preparation step is to decide if you want to use non-specific allocation, or if not what volume(s) you want the files on.

Z/vm Installation Guide

You should have at least 2000 tracks of disk space available. Upload the xmi file.

Use a binary file transfer (ftp? Ind$file?) to upload kicks-TSO-v1r5m0.xmi to the system as USERID.KICKS.V1R5M0.XMI (or some other name you like, but these instructions will call it USERID.KICKS.V1R5M0.XMI). You should select recfm=fb, lrecl=80 for the uploaded file. Since kicks-TSO-V1R5M0.xmi is about 10 megs it may take several minutes to upload. Some systems will require you to pre-allocate the upload file (or override the default space allocation for the upload). The clue is a B37 (etal) during the upload.

If that happens pre-allocate USERID.KICKS.V1R5M0.XMI like this dsn=userid.kicks.v1r5m0.xmi,unit=sysda,disp=(,catlg), space=(trk,(225,15)),dcb=(recfm=fb,lrecl=80,blksize=3200) Alternately, you could specify appropriate options to the file transfer program. For example, for ind$file you could add space(225,15) tracks 5.

'Receive' the uploaded file. Get to a TSO READY prompt.

Enter RECEIVE INDS(KICKS.V1R5M0.XMI) You might need to press enter a few more times at TSO. prompts. Delete USERID.KICKS.V1R5M0.XMIT, it's no longer needed.

You will find you have a new pds USERID.KICKS.V1R5M0.BIGPDS, most of whose members also need to be received. First member in the pds is $$V1R5M0 which is a REXX to do all the receives. Run without any optional arguments it will restore the KICKS non-VSAM datasets to non specific volumes with a high level qualifier (HLQ) of your userid, ie EXEC 'USERID.KICKS.V1R5M0.BIGPDS($$V1R5M0)' The first optional argument is an HLQ to use instead of your userid, ie EXEC 'USERID.KICKS.V1R5M0.BIGPDS($$V1R5M0)' 'otherHLQ' The second optional argument is the volser to use for specific volume allocation. EXEC 'USERID.KICKS.V1R5M0.BIGPDS($$V1R5M0)' '.

volid' Note the '.' in front of the volid above. That's a placeholder for a missing first optional argument. Of course both could be specified if desired, ie EXEC 'USERID.KICKS.V1R5M0.BIGPDS($$V1R5M0)' 'otherHLQ volid' Decide what you want to do, then Get to a TSO READY prompt Enter one of the above commands as you choose You will need to press enter a few dozen times at TSO. prompts.

Z/vm Program Directories

Delete USERID.KICKS.V1R5M0.BIGPDS, it's no longer needed. Customize KICKS for your USERID. Get to a TSO READY prompt Enter EXEC KICKSSYS.V1R5M0.CLIST(KFIX) Responding as appropriate to the query regarding the userid/prefix/literal to be used for customization.

If necessary edit the clist (ZFIX as called by KFIX) to obtain the desired customization and restart this step. When the clist finishes successfully you should see a 'Done' message above the next READY prompt. Edit USERID.KICKS.V1R5M0.INSTLIB(LOADMUR), which is batch jcl Change the jobcard as appropriate to conform to your shop standards and your own needs (do you want output be printed or held?). If you want specific volumes global change PUB002 to whatever volume you want the VSAM files allocated on; if you want non-specific volumes, global change PUB002 to '.' . Submit the job and make sure it runs ok. All condition codes in the JES log should be zero.

Edit USERID.KICKS.V1R5M0.INSTLIB(LOADTAC), which is batch jcl Change the jobcard as appropriate/ If you want specific volumes global change PUB002 to whatever volume you want the VSAM files allocated on; if you want non-specific volumes, global change PUB002 to. Submit the job and make sure it runs ok. All condition codes in the JES log should be zero.

Edit USERID.KICKS.V1R5M0.INSTLIB(LOADSDB), which is batch jcl Change the jobcard as appropriate If you want specific volumes global change PUB002 to whatever volume you want the VSAM files allocated on; if you want non-specific volumes, global change PUB002 to. Submit the job and make sure it runs ok. All condition codes in the JES log should be zero. Edit USERID.KICKSSYS.V1R5M0.INSTLIB(LODINTRA), which is batch jcl Change the jobcard as appropriate If you want specific volumes global change PUB002 to whatever volume you want the VSAM files allocated on; if you want non-specific volumes, global change PUB002 to. Submit the job and make sure it runs ok. All condition codes in the JES log should be zero.

Edit USERID.KICKSSYS.V1R5M0.INSTLIB(LODTEMP), which is batch jcl Change the jobcard as appropriate If you want specific volumes global change PUB002 to whatever volume you want the VSAM files allocated on; if you want non-specific volumes, global change PUB002 to. Submit the job and make sure it runs ok.

All condition codes in the JES log should be zero. Start KICKS Get to a TSO READY prompt Enter EXEC KICKSSYS.V1R5M0.CLIST(KICKS) READY kicks KICKS version 1.5.0(0) startup using SIT=1$, which with command line and stdin overrides results in. V marc unpack kicks vmarc a = = a (olddate replace notrace 5. Build the VSAM environment on an empty mini-disk. This is in three steps. Define the DOS environment to KICKS by updating and assembling the FCT (file control table); then run the PREVSAM EXEC to dos format the vsam mini-disk; and finally run the POSTVSAM EXEC to define the vsam catalog and space, and to define and load the sample files. Edit KIKFCT1$ ASSEMBLE K and change the CATXXXX arguments in lines 3-5 per the instructions in the of this guide.

Especially note/change CATUSER, the CMS userid of the 'owner' of the mini-disk (probably your own id), CATLNK1, the disk address by which the mini-disk is defined in the system directory, CATPASS, the write password for the mini-disk. The other arguments (CATLNK2, CATFM, CATVOL) are probably OK as they are. You will also need to re-assemble the FCT, which you do by entering the following command.

Prevsam DEV xxx DOES NOT EXIST About to erase and DOS format your xxx mini disk! Please type YES now to confirm this action.

YES DASD 0xxx DETACHED Filemode O not accessed Device 0222 does not exist Device 0xxx does not exist 222 replaces O (222) ICKDSF - CMS/XA/ESA DEVICE SUPPORT FACILITIES 17.0 INIT UNIT(222) - PRG NVFY VOLID(VSAMIN) - FBAVTOC(END) ICK00700I DEVICE INFORMATION FOR 0222 IS CURRENTLY AS FOLLOWS: PHYSICAL DEVICE = 3370-2 STORAGE CONTROLLER = 3880 STORAGE CONTROL DESCRIPTOR = 01 DEVICE DESCRIPTOR = 04 ICK01731I MAP FUNCTION NOT SUPPORTED FOR MINI-DISKS ICK00001I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 0 After 'I CMS' press ENTER you type enter here. Define the VSAM catalog, space, sample files, and load test data into the sample files using the POSTVSAM EXEC. Kiktable pct 1$. In addition to Cobol programming, KICKS supports application development using the GCCCMS C compiler and libraries.You may want to download and install those next if you haven't already done so.

Find them at. Further testing of the execs, preprocessors, and compilers is recommended, and the easiest way to do this is to run the API test/demonstration execs in TESTCOB VMARC (for Cobol) and TESTGCC VMARC (for C). After that (and after trying the precompiled versions!), recompile the online example maps by reviewing then running the KIKSAMPM EXEC, then recompile the online example programs by reviewing then running the KIKSAMPP EXEC. Finally verify that the online examples work like the precompiled ones did. Note that these two execs run many back-to-back compiles and generate voluminous output - they'd be great candidates for CMSBATCH. Uninstalling KICKS. There is a KGONE EXEC that will delete all (at least most) of the KICKS distribution files from the A mini-disk (type KGONE A).

VM/370 These instructions are for use by a normal CMS user to perform an unassisted install of KICKS into his or her own CMS account. Instructions for systems programmers to install KICKS for general use are. KICKS is available from a number of sites, including the, so download a copy and review and accept the license. Unzip kicks-cms-v1r5m0.zip resulting in a single folder named kicks-cms-v1r5m0. The following files and folders will be within.

Kicks-cms-v1r5m0.vmarc - a VMARC file that you will upload to your system User's Guide - a folder containing this User's Guide. Note - Although a copy of the User's Guide is included in the distribution package you should always use the online version (at ) if possible as it is the most current. In particular, many installation problems can be resolved by reinstalling using the instructions in the online version! Kicks-license.txt - a text file of the license you agreed to when you downloaded the KICKS package. Readme.txt - a text file with this information, and telling you to go to the User's Guide Installation section to continue the install. Prepare for install:.

The VM/370 6-pack 1.2 system may be downloaded from. The X'58' full screen support package may be downloaded from the 'FILES' area (most current as of this writing is called 'diag58v108.zip'). This may not be absolutely necessary if you install the optional MECAFF console support, but these instructions assume you do have X'58' support installed.

The MECAFF tools package may be downloaded from the 'FILES' area (most current as of this writing is called 'mecaff-tools-and-console-1.2.5.zip'). Be sure you install the 'static linked' version of the MECAFF tools. This is necessary because KICKS uses the DOS/VSAM components of VM/370, whose use will cause the 'dynamically linked' versions of the MECAFF tools to abend (and require you to re-IPL CMS all the time, very irritating. The CMSUSER account on the VM/370 6-pack has empty 192, 193, 194, and 195 mini-disks. The KICKS install will modify CMSUSER's PROFILE EXEC to release/detach the 194 mini-disk, and to access the 195 mini-disk as 'K'. All KICKS permanent non-vsam files will be installed onto the 195 mini-disk that will be accessed as 'K'.

The 194 mini-disk will be DOS formatted. A vsam master catalog and vsam space will be allocated on it, and the KICKS sample vsam files will be defined and loaded into that vsam space. The 194 mini-disk will otherwise remain unlinked so that not just CMSUSER, but any KICKS user can access the vsam files. KICKS or associated programs, run by any user, will access this 194 mini-disk as 'O'. Ensure you are not using CMSUSER's 194 or 195 mini-disks before you start the KICKS install!!

Unload installation package from tape. Logon to MAINT from a full screen capable 3270 session. Edit SIXPACK DIRECT to change CMSUSER's default storage size down to 14M (so that there is room for the DOS/VSAM segment) change 'USER CMSUSER CMSUSER 15M 16M G' to 'USER CMSUSER CMSUSER 14M 16M G' then after you save that change. V marc unpack kicks vmarc k = = k (olddate replace notrace 5. Build the VSAM environment on the 194 mini-disk. This is in three steps.

Define the DOS environment to KICKS by updating and assembling the FCT (file control table); then run the PREVSAM EXEC to dos format the vsam mini-disk; and finally run the POSTVSAM EXEC to define the vsam catalog and space, and to define and load the sample files. Edit KIKFCT1$ ASSEMBLE K and, if necessary, change the CATXXXX arguments in lines 3-5 per the instructions in the of this guide. This will probably be unnecessary since KICKS comes with these arguments pre-configured for the VM/370 6 pack system. If you change nothing just quit out of the editor. If you do change something you will also need to re-assemble the FCT, which you do by entering the following command. Prevsam DEV 194 DOES NOT EXIST About to erase and DOS format your 194 mini disk! Please type YES now to confirm this action.

Z/vm Performance

YES DASD 194 DETACHED DISK 'O' NOT ACCESSED. DEV 222 DOES NOT EXIST O (222) R/W - DOS New file: EDIT: NO FILES PURGED PUN FILE 0782 TO CMSUSER COPY 01 NOHOLD PUN FILE 0783 TO CMSUSER COPY 01 NOHOLD IBCDASDI has been IPLed to format the vsam disk. Press ENTER to see the 'DEFINE INPUT' request - then type 'INPUT=2540,00C' and press ENTER When done (almost immediately), type 'I CMS' and press ENTER, - then ENTER again to finish the IPL, Finally type POSTVSAM and press ENTER you type enter here. IBC105A DEFINE INPUT DEVICE. DASDI 7.91 input=2540,00c DASDI 7.91 JOB 'DOS INIT 194 AS VSAMIN' MSG TODEV=1052,TOADDR=009 DADEF TODEV=3350,TOADDR=222,IPL=NO,VOLID=SCRATCH,CYLNO=0115 VLD NEWVOLID=VSAMIN,OWNERID=CMSUSER VTOCD STRTADR=1,EXTENT=15 END IBC163A END OF JOB. CP ENTERED; DISABLED WAIT PSW '000EEEE' i cms.

Define the VSAM catalog, space, sample files, and load test data into the sample files using the POSTVSAM EXEC. Direct sixpack DMKUDR476I System Directory loaded from volume VM50-1 EOJ DIRECTORY UPDATED AND ON LINE. In addition to Cobol programming, KICKS supports application development using the GCCCMS C compiler and libraries. These are already installed on the VM/370 6-pack, but unfortunately the installed library has a bug that prevents it's use with KICKS. A fixed (and more up-to-date) version of that library is included with KICKS as PDPCLIB TXTLIB on the K mini-disk and will be used when any of the standard KICKS compile exec's are used. If you want to use it with other execs (ie, the standard GCC execs) you can copy it to the system Y disk by logging on to MAINT, releasing the Y disk, accessing 19E as Y disk, copying PDPCLIB TEXTLIB from CMSUSER K disk to the MAINT Y disk, then releasing Y again and accessing 19E as Y/S.

Link cmsuser 195 111 acc 111 k rel y acc 19e y copy pdpclib txtlib k = = y (replace rel y acc 19e y/s rel k (det. Further testing of the execs, preprocessors, and compilers is recommended, and the easiest way to do this is to run the API test/demonstration execs in TESTCOB VMARC (for Cobol) and TESTGCC VMARC (for C). After that (and after trying the precompiled versions!), recompile the online example maps by reviewing then running the KIKSAMPM EXEC, then recompile the online example programs by reviewing then running the KIKSAMPP EXEC. Finally verify that the online examples work like the precompiled ones did.

Note that these two execs run many back-to-back compiles and generate voluminous output - they'd be great candidates for CMSBATCH. Uninstalling KICKS. KICKS can be uninstalled simply by re CMS formatting the 194 ( KICKS code) and 195 (dos vsam) mini-disks. You might also want to revert your PROFILE EXEC to access these mini-disks as F and G respectively. There is also a KGONE EXEC that will delete all (at least most) of the KICKS distribution files from the K (ie, 194) mini-disk (type KGONE K). This may make it easier to find any of your own files you want to save before you reformat.

Installing KICKS for many users (system install) Installing KICKS for many users is much the same as installing it for one. The effort is not so much in the installation as in deciding exactly what to provision to users who need access to it. Following is the simplest case: KICKS will be installed in one place and all TSO/CMS users will have fully shared access to it.