[{"_1":2,"_169":-5,"_170":-5},"loaderData",{"_3":4,"_18":19,"_25":26,"_147":148},"root",{"_5":-5,"_6":-7,"_7":8,"_9":-7,"_10":11,"_12":-7,"_13":14,"_15":16,"_17":11},"currentUser","primaryEmail","siteVerification","6LeIxAcTAAAAAJcZVRqyHh71UMIEGNQ_MXjiZKhI","toast","enableDev",false,"incidentStatus","theme","system","contrast","normal","dockerRebrandTour","routes/_layout",{"_20":-5,"_21":22,"_23":11,"_24":22},"username","isAskGordonEnabled",true,"showMinimalLanding","showHoneypotTrap","routes/_layout.r.$namespace.$reponame",{"_27":28,"_29":-5,"_30":11,"_31":11,"_32":33,"_34":35,"_36":-5,"_37":11,"_38":39,"_93":-5,"_94":95,"_135":-5,"_136":11,"_137":22,"_138":11,"_139":11,"_140":-5,"_141":11,"_142":-5,"_143":144,"_145":96,"_146":-7},"canonicalUrl","https://hub.docker.com/r/praths/mvs-tk5/tags","mcpServer","canSeeDockerfile","canSeeAutobuilds","namespace","praths","reponame","mvs-tk5","cloudBuildSource","isAutobuildsAvailable","repo",{"_40":41,"_47":48,"_50":51,"_52":53,"_54":11,"_55":56,"_57":58,"_59":60,"_43":35,"_32":33,"_62":63,"_64":49,"_65":66,"_67":68,"_69":70,"_71":-5,"_72":73,"_74":75,"_76":11,"_77":33,"_78":79,"_84":11,"_85":86,"_90":33,"_91":92},"categories",[42],{"_43":44,"_45":46},"name","Operating systems","slug","operating-systems","content_types",[49],"image","date_registered","2024-02-17T15:20:52.825743Z","description","MVS TK5 is an implementation of OS/VS2 MVS Release 3.8J running on SDL-Hercules-390 on ARM64","is_private","last_updated","2025-03-04T08:58:37.655912Z","last_modified","2025-03-03T19:54:11.905252Z","media_types",[61],"application/vnd.docker.container.image.v1+json","pull_count",986,"repository_type","star_count",3,"status",1,"status_description","active","source","collaborator_count",0,"full_description","# MVS 3.8j - TK5 Update 4\nMVS TK5 is an implementation of OS/VS2 MVS Release 3.8J. The successors to MVS 3.8, MVS/XA, MVS/ESA, OS/390 and z/OS all demonstrate their OS/VS MVS 3.8 heritage. \n\nThis repository contains the [TK5 Update 2]( https://www.prince-webdesign.nl/tk5) implementation provided by Rob Prins for ARM64 platforms using SDL-Hercules-390 \n\n## Changes to TK5 Update 4\n- Replace embedded Hercules with current version of [SDL-Hercules-390](https://github.com/SDL-Hercules-390/hyperion) \n- Added support for user defined DASD (**D**irect **A**ccess **S**torage **D**evice i.e., external disks) using docker volume\n## Running TK5 as container\nWhen running the container, hercules, the mainframe System/370 emulator, will be started, configured to run MVS 3.8j, and an IPL of TK5 is performed. Once MVS has started, it can be accessed using a TN3270 emulator using port 3270. The Hercules console can be access by connecting to using any web browser.\n### Downloading and running TK4 for the first time\n```\ndocker run --name mvs-tk5 -it -p 3270:3270 -p 8038:8038 --cap-add=sys_nice --mount src=mvs-tk5-dasd.usr,target=/opt/tk5/dasd.usr praths/mvs-tk5\n```\n| Parameters | Description |\n| :--- | :-- |\n| --name \\ | Name of the container to be created, e.g. **mvs-tk5** |\n| -it | Attach interactive terminal to view log output | \n| -p \\:\\ | Maps ports between host and container
Port 3270: Telnet 3270 to access MVS
Port 8038 to access the Hecules console |\n| --cap-add=sys_nice | Grants the container the `CAP_SYS_NICE` capability, which allows the container to raise process nice values, set real-time scheduling policies, set CPU affinity, and other operations. |\n| --mount src=\\,target=/opt/tk5/dasd.usr | Uses the volume specified by \\ and maps it to the containers file system as specified by target=
Creates a volume, e.g. **mvs-tk5_dasd.usr** and maps it to the containers internal file system as **/opt/tk5/dasd.usr** to mount additional DASD[^1] that are not part of the system configuration in a persistent storage.
By default all DASD are stored in the directory /opt/tk5/dasd, user created DASD should be placed in **/opt/tk5/dasd.usr**
Details on how to create additional DASD and configure MVS to use them can be found in the section **Customizing MVS=TK5** |\n\nLoading of MVS-TK5 is completed when the following is shown on the Hercules console:
\n $\"image\"$ \n\n### Login to MVS-TK5\n- Connect to port 3270 on your local host using an 3270 Emulator\n- Logon using **HERC02** as user and **CUL8TR** as password\n
$\"image\"$ \n $\"image\"$ \n $\"image\"$ \n- Accept the welcome messages until you see the ISPF Primary Menu\n
$\"image\"$ \n\n## Customizing TK5\n### Changing the Timezone\n- Select **2** (Edit) from the ISPF primary option menu\n- Select **SYS1.PARMLIB(PARMTZ)**\n
$\"image\"$ \n- Change the Time Zone setting
\n Syntax:
\n D,HH[.MM[.SS]]

\n Parameters:
\n \"E\" or \"W\" to specify a time zone east or west or Greenwich Mean Time (GMT)\n HH specifies the number of hours deviation from GMT (00-12)\n MM specifies the number of minutes. Optional parameter. (00-59)\n SS specifies the number of seconds. Optional parameter (00-59)\n\n $\"image\"$ \n\n### Enabling the CBT Catalogue\nTo make the CBT Volumes accessibles submit job **SYS1.SETUP.CNTL(MVS0170) [issue **sub** on the Command line when viewing/editing the dataset]. This connects the SYS1.UCAT.CBT user catalog to the master catalog and defines the CBT, CBTCOV, CBT072, CBT129, CBT249, CBT429 HLQ as aliases.\n\nRecommendation:
\nChange MSGCLASS from 'A' to 'H' so that the result of the job can be viewed\n\n $\"image\"$ \n\n## Adding User DASD\nThere are different DASD types that vary in capacity; typical models as 3330, 3340, 3350, 3380, 3390, etc. \n\nMVS communicates to DASD through addresses. MVS-TK5 has assigned the following address ranges for DASD devices:\n $\"image\"$ \n\nIn MVS-TK5 the following addresses for DASD Model 3350 are in use:\n| Address | Volume |\n| :------ | :----- |\n| 0140 | WORK00 |\n| 0148 | MVSRES |\n| 0149-014A | SMP001, SMP002 |\n| 014B-014C | SMP003, SMP004 |\n| 0240-0241 | PUB000, PUB010 |\n| 0248 | MVSDLB |\n| 0340-0342 | CBT000, CBT001, CBT002 |\n| 0343 | CBTCAT |\nFor the actual use of addresses refer to the **conf/tk5-.cnf** file\n\n### Create and configure a user DASD\n1. Create the DASD
\n For our purpose we want to create the following volume to store user data:\n | Address | Model | Volume |\n | :------ | :---- | :----- |\n | 034A | 3350 | USR000 |\n \n To create the DASD image hercules provides a utility called **dasdinit**. The terminal console of the container can be accessed either by using the Docker Dashboard or by launching a terminal session using `docker exec -it mvs-tk5 /bin/bash` and use the following command to create the DASD. \n ```\n dasdinit -z -a /opt/tk5/dasd.usr/usr000.34a 3350 USR000\n ````\n This creates a new DASD of Type 3350 with the Volume name **USR000**\n >HHC02499I Hercules utility dasdinit - DASD image file creation program - version 4.5.0.10830-SDL-g58578601-modified
\n >HHC01414I (C) Copyright 1999-2022 by Roger Bowler, Jan Jaeger, and others
\n >HHC01417I ** The SoftDevLabs version of Hercules **
\n >HHC01415I Build date: Mar 28 2023 at 10:51:26
\n >HHC00462I 0:0000 CKD file /opt/tk5/dasd.usr/usr000.34a: creating 3350 volume USR000: 560 cyls, 30 trks/cyl, 19456 bytes/track
\n >HHC00460I 0:0000 CKD file /opt/tk5/dasd.usr/usr000.34a: 560 cylinders successfully written
\n >HHC02423I DASD operation completed
\n2. Attach DASD
\n In order for MVS to communicate with the DASD it must be attached. To attach the DASD at address 34A in the running configuration use the following command in the Hercules console:\n ```\n attach 034a 3350 dasd.usr/usr000.34a\n ```\n $\"image\"$ \n3. Initalize the DASD Image for use by MVS\n Although the dasdinit program creates the raw DASD image, MVS requires additional information that is not written by dasdinit. The following JCL initalizes newly created DASD as Volume **USR000** using address **34A**, and assigns 1 Cylinder (30 Tracks) for the VTOC.\n \n ```\n //INITDASD JOB (INITDASD), \n // 'Initialize DASD', \n // CLASS=A, \n // MSGCLASS=H, \n // MSGLEVEL=(1,1) \n //********************************************************************\n //* \n //* Name: (DEFCAT) \n //* \n //* Desc: Initializes a DASD for use with MVS \n //* \n //********************************************************************\n //STEP1 EXEC PGM=ICKDSF,REGION=4096K \n //SYSPRINT DD SYSOUT=* \n //SYSIN DD * \n INIT UNITADDRESS(34A) NOVERIFY VOLID(USR000) OWNER(HERCULES) - \n VTOC(0,1,30) \n // \n ```\n You will be asked to confirm that you actually want to initialize the volume at the address specified:\n >*00 ICK003D REPLY U TO ALTER VOLUME 34A CONTENTS, ELSE T\n\n The reply of U allows the initialization to proceed. There will be a number of informational messages printed in the SYSPRINT output during the executing of ICKDSF. The most important thing to verify is that the return code for the job is 0000.\n \n $\"image\"$ \n\n4. Set the volume online and mount it with the appropriate storage use class
\n After the volume is initialized, it must be placed online before MVS will be able to allocate the volume to allow jobs to create datasets on it. On the MVS console issue the command \n ```\n /v

,online`\n ```\n $\"image\"$ \n\n After the volume is set online it must be mounted.\n ```\n /m 34a,vol=(sl,usr000),use=private\n ```\n $\"image\"$ \n \n By using use=private new datasets will be created on this volume only if the user (via JCL or the TSO ALLOCATE command) specifies the volume serial of this disk volume.\n \n5. Add the new volume to the MVS & Hercules configuration so it will be mounted automatically\n - Edit MVS Configuration
\n By modifying **SYS1.PARMLIB(VATLST00)** MVS will be instructed to automatically mount the volume, if accessible, and assign storage class 2 (Private)\n ```\n USR000,0,2,3350 ,N User Volume 1 \n ```\n $\"image\"$ \n - Edit Hercules Configuration
\n Modify the file usr_dasd.cnf in the folder /opt/tk5/dasd.usr to automatically attach the newly created dasd at address 34a. This file is referenced as include in the MVS-TK5 base configuration file (/opt/tk5/conf/tk5-.cnf)\n\n ```\n #\n # User Added DASD\n #\n 034a 3350 dasd.usr/usr000.34a\n ```\n\n To modify the file use the Docker Dashboard or use the following command to edit it\n ```\n docker exec -it mvs-tk5 nano /opt/tk5/dasd.usr/usr_dasd.cnf\n ```\n6. Set Up User Catalogs
\n Generally, when adding new storage space to the system, it is also a good time to think about how that storage space will integrate with the catalog structure in place for the system.\n\n During System Generation, a VSAM Master Catalog was created. It resides on MVSRES and the dataset name of the catalog itself is SYS1.VSAM.MASTER.CATALOG. Although any new datasets you created can be catalogued in the Master Catalog, it is not considered a good practice and would undoubtedly not be allowed in any real world shop.\n \n To create a User catalog called **UCUSR000** that resides on the new volume **USR000** that will be connected to the master catalog, submit the following JCL:\n ```\n //DEFCAT JOB (DEFCAT), \n // 'Define User Catalog', \n // CLASS=A, \n // MSGCLASS=H, \n // MSGLEVEL=(1,1) \n //********************************************************************\n //* \n //* Name: (DEFCAT) \n //* \n //* Desc: Defines a User for the volume(s) specified by //VOL1 \n //* and create a user catalog on the voluem specifice in the \n //* VOLUME (xxxxxx) parameter in DEFINE USERCATALOG. \n //* \n //* After creating the User catalog, define an alias for all \n //* DNS with the High level Qualifer specified in NAME(xxxxx) \n //* and relate it to the User catalog \n //* \n //********************************************************************\n //STEP1 EXEC PGM=IDCAMS,REGION=4096K \n //SYSPRINT DD SYSOUT=A \n //VOL1 DD VOL=SER=USR000,UNIT=3350,DISP=OLD \n //SYSIN DD * \n DEFINE USERCATALOG - \n (NAME (UCUSR000) - \n VOLUME (USR000) - \n CYLINDERS (20) - \n FOR (9999) - \n BUFFERSPACE (8192) ) \n \n /* Define Alias for all dataset start with PRATHS */ \n DEFINE ALIAS(NAME(PRATHS) RELATE (UCUSR000) ) \n // \n ```\n### Connecting an existing volume to a system\nWhen a volume is brought into the system from a prior functioning system that has its own User Catalog on the volume, the volume must be attached, added to the MVS configuration, and the catalog connected to the master catalog\n\n1. Copy DASD file
\n Copy the DASD file to /opt/tk5/dasd.usr directory, respectively run docker using `docker run --name mvs-tk5 -it --mount src=mvs-tk5_dasd.usr,target=/opt/tk5/dasd.usr -p 3270:3270 -p 8038:8038 mvs-tk5:latest` with a docker volume that already contains the DASD files\n \n2. Attach the DASD file mount the volume\n - Attach DASD & mount it\n Attach the DASD using the following command in the MVS console:\n ```\n attach 034a 3350 dasd.usr/usr000.34a\n ```\n Once the DASD is attach, set it online using `/v 34a,online` and mount it `/m 34a,vol=(sl,usr000),use=private`\n\n3. Modify the MVS configuration to automatically mount the DASD\n - Edit MVS Configuration
\n By modifying **SYS1.PARMLIB(VATLST00)** MVS will be instructed to automatically mount the volume, if accessible, and assign storage class 2 (Private)\n ```\n USR000,0,2,3350 ,N User Volume 1 \n ```\n $\"image\"$ \n\n - Edit Hercules Configuration
\n Modify the file /opt/tk5/dasd.usr/usr_dasd.cnf to automatically attach the newly created dasd at address 34a. This file is referenced as include in the TK5- base configuration file (/opt/tk5/conf/tk5-.cnf)\n ```\n #\n # User Added DASD\n #\n 034a 3350 dasd.usr/usr000.34a\n ```\n\n4. Import existing Catalog
\n As the existing volume already contains a User Catalog it must be imported and connected to the master catalog using:\n ```\n //IMPCAT JOB (IMPCAT), \n // 'Import User Catalog', \n // CLASS=A, \n // MSGCLASS=H, \n // MSGLEVEL=(1,1) \n //********************************************************************\n //* \n //* Name: (IMPCAT) \n //* \n //* Desc: Imports an existing User catalog and creates alias(es) \n //* \n //********************************************************************\n //STEP1 EXEC PGM=IDCAMS,REGION=4096K \n //SYSPRINT DD SYSOUT=A \n //VOL1 DD UNIT=3350,DISP=OLD,VOL=SER=USR000 \n //SYSIN DD * \n IMPORT CONNECT OBJECTS((UCUSR000 VOLUME(USR000) DEVT(3350))) \n DEFINE ALIAS(NAME(PRATHS) RELATE(UCUSR000)) \n //\n ```\n\n## Running TK5 as a docker service using Docker Compose\nThe following is an example of the compose.yaml file to run mvs-tk5. In addition to the volume for user defined DASD additional volumes are being used for the following devices for easier access and to to minimise run-time changes to the container.\n| Device | Description | Location in TK5 file system |\n| :--- | :--- | :--- |\n| User DASD | User defined DASD as described above | /opt/tk5/dasd.usr |\n| Logs | TK5 Log files | /opt/tk5/log |\n| Tape | Tapes | /opt/tk5/tape |\n| Printer | Printer spool files | /opt/tk5/prt |\n| Punch | Card Reader | /opt/tk5/pch |\n\n```\n#\n# Define services\n#\nservices:\n tk5:\n image: praths/mvs-tk5:latest\n container_name: mvs-tk5\n stdin_open: true # docker run -i\n tty: true # docker run -t\n cap_add: \n - SYS_NICE\n network_mode: bridge\n ports: \n - 3270:3270\n - 8038:8038\n volumes:\n - dasd.usr:/opt/tk5/dasd.usr\n - log:/opt/tk5/log\n - tape:/opt/tk5/tape\n - prt:/opt/tk5/prt\n - pch:/opt/tk5/pch\n restart: no\n\nvolumes:\n #\n # System DASD\n #\n dasd.sys:\n #\n # User DASD\n #\n dasd.usr:\n driver: local\n driver_opts:\n type: 'none'\n o: 'bind'\n device: '/home/user/tk5/dasd.usr'\n #\n # System Logs\n #\n log:\n driver: local\n driver_opts:\n type: 'none'\n o: 'bind'\n device: '/home/user/tk5/log'\n #\n # Tape Devices\n #\n tape:\n driver: local\n driver_opts:\n type: 'none'\n o: 'bind'\n device: '/home/user/tk5/tape'\n #\n # Printers\n #\n prt:\n driver: local\n driver_opts:\n type: 'none'\n o: 'bind'\n device: '/home/user/tk5/prt'\n #\n # Card Readers\n #\n pch:\n driver: local\n driver_opts:\n type: 'none'\n o: 'bind'\n device: '/Users/praths/Documents/tk5/pch'\n```","has_starred","hub_user","immutable_tags_settings",{"_80":11,"_81":82},"enabled","rules",[83],".*","is_automated","permissions",{"_87":22,"_88":11,"_89":11},"read","write","admin","user","storage_size",2836586009,"orgData","recentTags",[96],{"_97":49,"_98":99,"_100":101,"_102":103,"_104":105,"_106":107,"_55":124,"_125":99,"_126":33,"_127":61,"_43":128,"_129":130,"_131":114,"_132":124,"_133":70,"_134":22},"content_type","creator",4550052,"digest","sha256:acd4520773523da72705b7d0d32091dd1fa2b525198b792e42c530d2fffc97a8","full_size",708730426,"id",605239303,"images",[108],{"_109":110,"_100":101,"_111":112,"_113":114,"_115":116,"_117":118,"_119":112,"_120":-5,"_121":103,"_67":70,"_122":123},"architecture","arm64","features","","last_pulled","2026-11-01T16:47:53.019076207Z","last_pushed","2025-03-04T08:58:36.243756085Z","os","linux","os_features","os_version","size","variant","v8","2025-03-04T08:58:36.565604Z","last_updater","last_updater_username","media_type","latest","repository",23228609,"tag_last_pulled","tag_last_pushed","tag_status","v2","sbxKitMetadata","isPotentialSpam","isHubSbxKitsEnabled","showSbxRunInCloud","showSbxLogoOverride","sbxTrademarkText","displaySecurityMetadata","tagAttestations","tagsHaveAttestations",[],"selectedTag","attestationsUrl","routes/_layout.r.$namespace.$reponame.tags",{"_38":149,"_157":158,"_143":167,"_168":11},{"_40":150,"_47":152,"_50":51,"_52":53,"_54":11,"_55":56,"_57":58,"_59":153,"_43":35,"_32":33,"_62":63,"_64":49,"_65":66,"_67":68,"_69":70,"_71":-5,"_72":73,"_74":75,"_76":11,"_77":33,"_78":154,"_84":11,"_85":156,"_90":33,"_91":92},[151],{"_43":44,"_45":46},[49],[61],{"_80":11,"_81":155},[83],{"_87":22,"_88":11,"_89":11},"tags",{"_159":68,"_160":-5,"_161":-5,"_162":163},"count","next","previous","results",[164],{"_97":49,"_98":99,"_100":101,"_102":103,"_104":105,"_106":165,"_55":124,"_125":99,"_126":33,"_127":61,"_43":128,"_129":130,"_131":114,"_132":124,"_133":70,"_134":22},[166],{"_109":110,"_100":101,"_111":112,"_113":114,"_115":116,"_117":118,"_119":112,"_120":-5,"_121":103,"_67":70,"_122":123},[],"canDeleteTags","actionData","errors"]

praths/mvs-tk5

Tags for praths/mvs-tk5