There are several methods that may be used to transfer an XMIT to MVS 3.8j, and I have discussed these methods in other areas of my site, but for this application I will be using the quickest, single-step method, which is to use the program RECV370 to read the XMIT file on the host system through an emulated MVS card reader and create the dataset on MVS that is contained within the XMIT file. Submit the job to MVS to transfer the XMIT dataset to MVS and unpack it. I find little use for a security system in an environment where I am the sole user, and having one active is simply a nuisance. I will be preparing a new 3350 DASD image to contain the KICKS system, so that is the first step in restoration of the installation archive on my MVS 3.8j system. This archive contains the installation archives for both TSO and CMS, so you will need to extract from the archive the folder kicks-tso-v1r5m0, which contains the necessary files for installing on MVS 3.8j as well as the installation and documentation for KICKS. The dataset will be placed on volume KICKS0, which you prepared in the step above, and it will be cataloged in the User Catalog UCKICKS0.
1892. It was called a “musical farce” rather than “musical comedy,” but it is really the first example of the new genre. I have chosen to use a 3350 image, rather than a larger capacity DASD type, because a 3350 is more than adequate to hold the initial KICKS datasets and allow for quite a bit of user datasets to still be created on the same volume. Of these, 26 are additional embedded XMIT files that will be expanded to create the KICKS installation datasets. KICKS cannot support the volume of users that CICS is able to, but has been demonstrated to be capable of supporting several hundred simultaneous users. Save the changes, then log off and back on so that the change becomes active for your TSO session. I guess back then there was a big problem with “impious”comedians & the future Carl Levitt was to rectify it. The catalogued procedure that is used to create TSO sessions is located in SYS1.PROCLIB and, unless there have been modifications since the system was generated, the name of the member is IKJACCNT.
We will be installing the system with all KICKS datasets having a High Level Qualifier of KICKS, so ‘system’ datasets will be recognizable as KICKS.KICKSSYS. The one you should select is KICKS, which is the second one presented. In the JCL above, the input dataset (XMITIN DD statement), you are specifying the exact address of a card reader that is emulated by Hercules. If you write applications that open many VSAM datasets simultaneously, it may be necessary to increase the size of your REGION, which is defined by the SIZE parameter of the TSO User ID in the TSO ACCOUNT command. There is a prototype job in SYSC.JCLLIB(RECV370) that may be quickly tailored to the needed requirements. Each of these jobs create test data for KICKS example transactions that have been supplied with KICKS. KICKS is also an excellent platform for learning CICS programming skills. KICKS may also be used to develop applications under MVS 3.8j that may then be uploaded to an IBM system running z/OS and CICS, where they may then be compiled and executed under CICS.
The MVS 3.8j systems I build and use do not have any security system installed. The address specified must match a device in your MVS system that is defined as a card reader and that card reader must not be managed by JES2. This change is only required if you are using a system built from my MVS 3.8j installation instructions and have installed the SYSCPK volume. If you are installing on a system where a security system is installed, it may be necessary to make additional allowances for KICKS to function properly under the control of a security system. However, that CLIST, and probably the CLIST that will be used to start the KICKS system later, require the capability of dynamically allocating a large number of datasets as they execute. A CLIST is provided that will assist in the customization of the KICKS installation. On the Hercules command window, initialize the card reader to point to the file on your host Operating System that holds the XMIT to be transferred. Note: This command specifies address x’01c’ which is the correct address for an MVS system built using my instructions. You should specify the correct path to the file in place of in the example command.