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. 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. 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. 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.
Z/vm Monitor Records
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.
4.00 Written in Website, Hercules is a computer allowing software written for computers (, and ) and for mainframes (such as machines) to run on other types of computer hardware, notably on low-cost. Although there are other mainframe emulators performing a similar function, Hercules is significant in enabling private individuals to run mainframe computer software on their own personal computers. Hercules runs under multiple parent including, and and is released under the license. It is analogous to and in that it emulates instructions and select peripheral devices only.
A vendor (or distributor) must still provide an operating system, and the user must install it. Hercules was notably the first mainframe emulator to incorporate 64-bit support, beating out commercial offerings. Roger Bowler, a mainframe systems programmer, started development of the Hercules emulator in 1999. Contents. Design The emulator is written almost entirely in.
Its developers ruled out using machine-specific code to avoid problems with portability even though such code could significantly improve performance. There are two exceptions: Hercules uses hardware assists to provide inter-processor consistency when emulating multiple CPUs on SMP host systems, and Hercules uses assembler assists to convert between and big-endian data on platforms where the operating system provides such services and on / processors. Operating systems status Hercules is technically compatible with all IBM mainframe operating systems, even older versions which no longer run on newer mainframes. However, many mainframe operating systems require vendor licenses to run legally. Newer licensed operating systems, such as, and are technically compatible but cannot legally run on the Hercules emulator except in very limited circumstances , and they must always be licensed from IBM. IBM's control code, which enables, and also require licenses to run. Operating systems which may legally be run without license from IBM on Hercules include:.
Older IBM operating systems including, and which are either or 'copyrighted software provided without charge.' .
The operating system may be available for educational and demonstration purposes upon request to its copyright holder,. Some of MUSIC/SP's features, notably networking, require z/VM (and thus an IBM license). However, a complete demonstration version of MUSIC/SP, packaged with the alternative Sim390 mainframe emulator, is available. The (MTS) version 6.0A has been tailored to run under Hercules. There is no known legal restriction to running operating systems and on the Hercules emulator. They run well on Hercules, and many Linux on System z developers do their work using Hercules.
Several distributors provide 64-bit z/Architecture versions of Linux, and some also provide -compatible versions. Mainframe Linux distributions include, GNU/Linux, and. Sine Nomine Associates brought OpenSolaris to System z, relying on features provided by z/VM. Emulation of those specific z/VM features for OpenSolaris is included starting with Hercules Version 3.07.
Certain unencumbered editors and utilities which can run on a mainframe without a parent operating system may be available to run on Hercules as well. Debian GNU/Linux running on Hercules Usage Hercules can be used as a development environment to verify that code is portable (across Linux processor architectures, for example), supports (SMP), and is 64-bit 'clean.' There is also a large community of current and former mainframe operators and programmers, as well as those with no prior experience, who use Hercules and the public domain IBM operating systems as a hobby and for learning purposes.
Most of the skills acquired when exploring classic IBM mainframe operating system versions are still relevant when transitioning to licensed IBM machines running the latest versions. The nature of Hercules means that anyone can produce their own customized version of the emulator. For example, a group of developers independent of the Hercules project implemented a hybrid mainframe architecture which they dubbed 'S/380' using modifications to both Hercules and to freely available classic versions of MVS (and later VM and DOS/VS), enhancing the operating systems with some degree of 31-bit (and as of 2016, 64-bit) binary compatibility with later operating system versions. Performance. This section needs additional citations for. Unsourced material may be challenged and removed.
(February 2014) It is difficult to determine exactly how Hercules emulation performance corresponds to real mainframe hardware, but the performance characteristics are understandably quite different. This is partially due to the difficulty of comparing real mainframe hardware to other PCs and servers as well as the lack of concrete, controlled performance comparisons. Performance comparisons are likely legally impossible for licensed IBM operating systems, and those operating systems are quite different from other operating systems, such as Linux. Hercules expresses its processing performance in. Due to the age of the earlier System/360 and System/370 hardware, it is a relatively safe assumption that Hercules will outperform them when running on moderately powerful hardware, despite the considerable overhead of emulating a computer architecture in software. However, newer, partially or fully configured System z machines outperform Hercules by a wide margin. A relatively fast dual processor X86 machine running Hercules is capable of sustaining about 50 to 60 MIPS for code that utilizes both processors in a realistic environment, with sustained rates rising to a reported 300 MIPS on leading-edge (early 2009) PC-class systems.
Hercules can produce peaks of over 1200 MIPS when running in a tight loop, such as in a synthetic instruction benchmark or with other small, compute-intensive programs. Tom Lehmann, co-founder of TurboHercules, wrote.We can run a reasonably sized load (800 MIPS with our standard package).
If the machine in question is larger than that, we can scale to 1600 MIPS with our quad Nehalem based package, and we have been promised an 8 way Nehalem EX based machine early next year that should take us to the 3200 MIPS mark. Anything bigger than that is replicated by a collection of systems. Hercules generally outperforms from the mid-1990s, which have an advertised peak performance of around 29 MIPS. Compared to the more powerful but still entry-level IBM Multiprise 2000 and 3000 mainframes (also from the 1990s), Hercules on typical x86 hardware would be considered a mid-range server in performance terms. For every mainframe after the 9672 Generation 1, Hercules would generally be the lowest end system.
For comparison, current high-end IBM systems can deliver over 52,000 MIPS per machine, and they have considerable I/O performance advantages. With the same number of emulated Sys Z processors, z/PDT is about 3 times faster than Hercules. Note that there are other non-functional system attributes beyond performance which are typically relevant to mainframe operators. TurboHercules In 2009, Roger Bowler founded TurboHercules SAS, based in France, to commercialize the Hercules technology. In July, 2009, TurboHercules SAS asked IBM to license to its customers for use on systems sold by TurboHercules. IBM declined the company's request. In March, 2010, TurboHercules SAS filed, alleging that IBM infringed EU antitrust rules through its alleged of mainframe hardware to its mainframe operating system, and the EC opened a preliminary investigation.
In November, 2010, TurboHercules announced that it had received an investment from Microsoft Corporation. In September, 2011, EC regulators closed their investigation without action. See also. References.
'6.1',: Hercules 390. (alphabetical) (list), The Open Source Initiative., Frequently-Asked Questions, EU: Hercules 390 Version 3. Michigan Terminal System Archive.
Retrieved Jan 29, 2013., MVS/380 project, Sourceforge. (Web log), Oracle., Turbo Hercules, archived from on 12 October 2011., European Commission, 26 July 2010. (PDF), TurboHercules, 23 November 2010, archived from on 10 March 2012., EC, last paragraph. External links. at Curlie (based on ). (Review on Tech-news.com). (MVS version 3.8, VM/CMS release 6, DOS/VS release 34, TSS/370 version 3).
(includes Turnkey MVS CD image).
Error description: Running zVM 5.4.0 as the primary OS on Hercules and performing a normal zVM 6.3.0 install as second level guest leads to iterative DSP005 system errors after restoration of the system mini disks and IPL of that newly generated system. During the first IPL the installation process is not finished yet.
The system restores certain disks using DDR restore. During this phase the DSP005 happens, the guest OS takes a dump and restarts.
Aeg lavamat protex. UsersManualGuide.com User Manual and User Guide for many equipments like mobile phones, photo cameras, motherboard, monitors, software, tv, dvd, and others.
After second DSP005 the system enters disabled wait state 9026. The collection of that dump information is quite difficult because the system is not installed completely and therefore there is no interactive environment to use.
DSP005: Explanation: The value of the processing unit timer is greater than it was at user dispatch. There is probably an error in switching timers.
User response: Examine the CP trace table and storage dump for possible solutions. CR12 points to the next available CP trace table entry after the failure. Hi Ivan, Yes indeed. Because of the information about the changes done regarding SIE, I compiled yesterday the latest committed version of Hyperion. In first level, up to now, I didn't face the problem of the TCP/IP start any more.
This is great. That bug of getting a network connection or not was a nightmare for many years. The online star.
However up to now I didn't face any DSP005 abends during a second level installation. Some weeks ago I run a first level installation of zVM 6.3.0 and more ore less it was successful. There the problem was that under some unknown conditions CMS faced a corrupted storage area in its nucleus and abended. That affected for instance the ipwizard exec and left the TCP/IP stack unconfigured.
So that problem seems to be fixed with the current change. This time I wanted to run a clean install for 6.3 to replace my old 5.4 version once and for good. Well, unfortunately, there seems to be still at leased one obstacle in front. If I can provide you with more info please let me know.
Hi Ivan, Yes indeed. Because of the information about the changes done regarding SIE, I compiled yesterday the latest committed version of Hyperion. In first level, up to now, I didn't face the problem of the TCP/IP start any more. This is great.
That bug of getting a network connection or not was a nightmare for many years. However up to now I didn't face any DSP005 abends during a second level installation. Some weeks ago I run a first level installation of zVM 6.3.0 and more ore less it was successful. There the problem was that under some unknown conditions CMS faced a corrupted storage area in its nucleus and abended. That affected for instance the ipwizard exec and left the TCP/IP stack unconfigured.
So that problem seems to be fixed with the current change. This time I wanted to run a clean install for 6.3 to replace my old 5.4 version once and for good.
Well, unfortunately, there seems to be still at leased one obstacle in front. If I can provide you with more info please let me know. Dear Florian, I have been unable to reproduce the DSP005 Abend during the 2nd level z/VM 6.3 (non-SSI) installation. Just to be sure, I tried it two times, but on both occasions all worked perfectly ending up with a clean z/VM 6.3 installation.
Both took indeed more than 6 hours. Down below you’ll find an extract of the installation log including the two DDR’s restores which I saw happening. I tried this under (one of the members of) my z/VM 6.3 (SSI).
However, somehow I don’t think that z/VM 5.4 as a 1st level z/VM is the cause of the DSP005, but perhaps rather the fact of z/VM 5.4 having been installed or running under Hercules prior to the TLP/ALB PURGE fix might have become somehow corrupt. I know this is a wild guess. But after the TLB/ALB PURGE fix, my z/VM 6.3 system’s DIRMAINT exhibited a CRC error, which I could correct by performing a USER DIRECT recovery (as prescribed in an IBM manual). This too, I thought, was caused the TLB/ALB PURGE problem (but then subsequently, after the TLB/ALB PURGE fix, recovered).
In summary, I think the TLB/ALB PURGE fix has resulted in SIE working perfectly. It might be improved on performance wise by purging a more limited number of TLB/ALB entries, but I think the functionality now is better than it ever was.
Z/vm Installation Guide
Perhaps even perfect. (As usual, until we discover the next problem of course ).
Dear Florian, I have been unable to reproduce the DSP005 Abend during the 2nd level z/VM 6.3 (non-SSI) installation. Just to be sure, I tried it two times, but on both occasions all worked perfectly ending up with a clean z/VM 6.3 installation. Both took indeed more than 6 hours. Down below you’ll find an extract of the installation log including the two DDR’s restores which I saw happening. I tried this under (one of the members of) my z/VM 6.3 (SSI). However, somehow I don’t think that z/VM 5.4 as a 1st level z/VM is the cause of the DSP005, but perhaps rather the fact of z/VM 5.4 having been installed or running under Hercules prior to the TLP/ALB PURGE fix might have become somehow corrupt.
I know this is a wild guess. But after the TLB/ALB PURGE fix, my z/VM 6.3 system’s DIRMAINT exhibited a CRC error, which I could correct by performing a USER DIRECT recovery (as prescribed in an IBM manual).
This too, I thought, was caused the TLB/ALB PURGE problem (but then subsequently, after the TLB/ALB PURGE fix, recovered). In summary, I think the TLB/ALB PURGE fix has resulted in SIE working perfectly. It might be improved on performance wise by purging a more limited number of TLB/ALB entries, but I think the functionality now is better than it ever was. Perhaps even perfect. (As usual, until we discover the next problem of course ). Thanks for the info John.
In my case, z/VM 6.3 (SSI) installed prior to TLB/ALB PURGE fix worked fine, apart from the intermittent known anomalies (e.g. TCPIP not always starting up, sometimes PIPE errors, etc.). Subsequent to the TLB/ALB PURGE fix all these went away. But then when I tried to perform another DIRM ADD (VMINSTAL, for my 2nd level z/VM install) DirMaint complained about a CRC error, which I recovered from using an earlier USER DIRECT backup following IBM’s published procedure. So to me this looked like the TLB/ALB PURGE problem had created an incorrect / corrupted CRC. Which is what leads me to now distrust any z/VM installed or running with that Hercules problem unsolved.
Z/vm Performance
In my case the CRC algorithm has not changed, but perhaps with the TLB/ALB PURGE problem it may have created wrong CRC’s. Thanks for the info John.
In my case, z/VM 6.3 (SSI) installed prior to TLB/ALB PURGE fix worked fine, apart from the intermittent known anomalies (e.g. TCPIP not always starting up, sometimes PIPE errors, etc.). Subsequent to the TLB/ALB PURGE fix all these went away. But then when I tried to perform another DIRM ADD (VMINSTAL, for my 2nd level z/VM install) DirMaint complained about a CRC error, which I recovered from using an earlier USER DIRECT backup following IBM’s published procedure. So to me this looked like the TLB/ALB PURGE problem had created an incorrect / corrupted CRC. Which is what leads me to now distrust any z/VM installed or running with that Hercules problem unsolved. In my case the CRC algorithm has not changed, but perhaps with the TLB/ALB PURGE problem it may have created wrong CRC’s.
Z/VM install files and Hercules z/VM install files and Hercules macromraco Jan 11, 2008 Hello guys, I'm new in this Mainframe world and I have a question: I have the z/VM installation DVD and would like to install it on Hercules. According to some posts that I saw in the list, it is not possible to install it using the DVD image itself, so is there a way to generate a tape or multiple CD structure with the DVD content, aggregate it to Hercules and install the z/VM os? Thank you guys! Marcio 7:28 pm Re: z/VM install files and Hercules azavedo Jan 13, 2008 Hi. I have not done this before but Hercules does not have the ability to install software available on CDs/DVDs (like the Load from CDROM or server option available from the Hardware Management Console HMC available for 'real iron'). I would be interested if there is a way to install mainframe software using CDs/DVDs.
In [email protected], 'macromraco' wrote: Hello guysI'm new in this Mainframe world and I have a question: I have the z/VM installation DVD and would like to install it on Hercules. According to some posts that I saw in the list, it is not possible to install it using the DVD image itself, so is there a way to generate a tape or multiple CD structure with the DVD contentaggregate it to Hercules and install the z/VM os?
Thank you guys! Marcio 9:10 pm Re: z/VM install files and Hercules Jay Maynard Jan 13, 2008 On Sun, Jan 13, 2008 at 09:10:15PM -0000, azavedo wrote: Hi. I have not done this before but Hercules does not have the ability to install software available on CDs/DVDs (like the Load from CDROM or server option available from the Hardware Management Console HMC available for 'real iron').
I would be interested if there is a way to install mainframe software using CDs/DVDs. Actually, it does. Mount the CD on your system, then start Hercules with an appropriate config file and say 'ipl ', where is the full path to the.ins file on the CD.
The reason that z/VM 5.2 and higher can't be installed from DVD on Hercules is not that it can't get to the data, but rather that that OS requires a device that Hercules doesn't emulate: a SYSG console, a 3270 device accessed through the service processor. It's been reported that you can install z/VM 5.2 and higher if you use an already-installed copy of z/VM as a driving system. Jay Maynard, K5ZC (Yes, that's me!) Buy Hercules stuff at 9:18 pm Copyright 2008.
Linux/VM: Getting Linux Running Under Hercules Last updated on: Sunday, July 06, 2008 Software. An S/390 Hardware Emulator Information. Community. News. Fun. Credits.
How to Get Linux Running Under Hercules This information was originally posted to the on April 17, 2002, by Florian La Roche.
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |