[{"_1":2,"_177":-5,"_178":-5},"loaderData",{"_3":4,"_18":19,"_25":26,"_152":153},"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,"_88":-5,"_89":90,"_140":-5,"_141":11,"_142":22,"_143":11,"_144":11,"_145":-5,"_146":11,"_147":-5,"_148":149,"_150":91,"_151":-7},"canonicalUrl","https://hub.docker.com/r/praths/tk4/tags","mcpServer","canSeeDockerfile","canSeeAutobuilds","namespace","praths","reponame","tk4","cloudBuildSource","isAutobuildsAvailable","repo",{"_40":41,"_42":43,"_45":46,"_47":48,"_49":11,"_50":51,"_52":53,"_54":55,"_57":35,"_32":33,"_58":59,"_60":44,"_61":62,"_63":64,"_65":66,"_67":-5,"_68":62,"_69":70,"_71":11,"_72":33,"_73":74,"_79":11,"_80":81,"_85":33,"_86":87},"categories",[],"content_types",[44],"image","date_registered","2023-04-05T05:02:17.499745Z","description","TK4- (OS/VS2 MVS 3.8j Service Level 8505) running on SDL-Hercules-390 on ARM64","is_private","last_updated","2023-05-07T15:43:23.259594Z","last_modified","2024-10-16T13:48:34.145251Z","media_types",[56],"application/vnd.docker.container.image.v1+json","name","pull_count",694,"repository_type","star_count",0,"status",1,"status_description","active","source","collaborator_count","full_description","The repositories contains images to run TK4- (OS/VS2 MVS 3.8j Service Level 8505) using Docker on the ARM64 architecture. Currently there are two versions available:\n| Tag | Version |\n| :--- | :--- |\n| latest | This is the official TK4-, Update 8 (OS/VS2 MVS 3.8j Service Level 8505) as as available on https://wotho.ethz.ch/tk4-/ |\n| rob | This edition, created by Rob Prims, which is based on the official TK4- Update 8 release contains various additions such as BREXX370 V2R5M2, RPF 1.9.4, etc. For details please refer to http://www.prince-webdesign.nl/tk4rob |\n## Changes to TK4 Update 8\nThe following changes were applied to the default TK4- Update 8 configuration as available on https://wotho.ethz.ch/tk4-/\n- Remove embedded Hercules\n- Remove all Windows related startup files\n- Remove support to run Hercules in unattended (daemon) mode\n- Modifed startup files\n- Added support for user defined DASD using docker volume\n## Running TK4 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 TK4- 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\nIt is recommended to create separate DASDs (**D**irect **A**ccess **S**torage **D**evice) to store data on MVS that is not part of the standard TK4- configuration. While by default all DASD are stored in the directory /opt/tk4/dasd, user created DASD should be placed in **/opt/tk4/dasd.usr** which is configured as docker volume to allow for persistent storage. \n\nDetails on how to create additional DASD and configure MVS to use them can be found in the section **Customizing TK4-**\n### Downloading and running TK4 for the first time\nTo run TK4- in a container requires that the container is started with the correct options:
\n*--name tk4* assigns the name **tk4** to the container. If omitted, docker will be assign a random name. For the purpose of this documentation, the container is referred to as **tk4**
\n*--it* runs the container interactive and assigns a terminal (tty). This allows to access the hercules console not only through the web interface but directly in a terminal session. If this option is omitted, TK4- will be started an the hercules console can be accessed through the web interface on \n*--mount src=tk4-dasd,target=/opt/tk4/dasd.usr* creates or connects an existing volume named **tk4-dasd** and mounts it as **/opt/tk4/dasd.usr** inside the container.
\n*-p 3270:3270[^1]* exports port 3270 of the container on the host using the same port number
\n*-p 8038:8038* exports port 8038 of the container on the host using the same port number
\n*--cap-add=sys_nice* grants the container the right to schedule thread priorities. Please note that due to a bug in docker desktop you may see errors/warning that thread priority cannot be set when the hercules emulator starts. \n\n Note:
\n By reassigning ports 3270, respectively 8038 to different ports on the host it would be possible to run multiple instances of TK4- in parallel, each of which can be accessed using a different port number. Should another container already be using any of these port numbers it cannot be launched using the default port numbers.
\n - Default TK4 configuration\n ```\n docker run --name tk4 -it -p 3270:3270 -p 8038:8038 --cap-add=sys_nice --mount src=tk4-dasd,target=/opt/tk4/dasd.usr praths/tk4\n ```\n - Rob Prins' enhanced TK4 edition\n ```\n docker run --name tk4.rob -it -p 3270:3270 -p 8038:8038 --cap-add=syc_nice --mount src=tk4-dasd,target=/opt/tk4/dasd.usr praths/tk4:rob\n ```\n Loading of TK4- is completed when the following is shown on the Hercules console:
\n $\"TK4$ \n## Customizing TK4-\n### Changing the Timezone\nTo change the timezone modify **SYS1.PARMLIB(PARMTZ)**

\nSyntax:
\nD,HH[.MM[.SS]]

\nParameters:
\n\"E\" or \"W\" to specify a time zone east or west or Greenwich Mean Time (GMT)\nHH specifies the number of hours deviation from GMT (00-12)\nMM specifies the number of minutes. Optional parameter. (00-59)\nSS 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### DASD\nThere are different DASD types that vary in capacity; typical models as 3330, 3340, 3350, 3380, 3390, etc. However, TK4- does not support DASD models later than than 3350. In this example a DASD of type 3350 is created which provides a capacity of approximately 300MB.\n\nMVS communicates to DASD through addresses. TK4- has assigned the following address ranges for DASD devices:\n $\"image\"$ \n\nIn TK4- 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/tk4-.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 tk4 /bin/bash` and use the following command to create the DASD. \n ```\n dasdinit -z -a /opt/tk4/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/tk4/dasd.usr/usr000.34a: creating 3350 volume USR000: 560 cyls, 30 trks/cyl, 19456 bytes/track
\n >HHC00460I 0:0000 CKD file /opt/tk4/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/tk4/dasd.usr to automatically attach the newly created dasd at address 34a. This file is referenced as include in the TK4- base configuration file (/opt/tk4/conf/tk4-.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 tk4 nano /opt/tk4/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/tk4/dasd.usr directory, respectively run docker using `docker run --name tk4 -it --mount src=tk4-dasd,target=/opt/tk4/dasd.usr -p 3270:3270 -p 8038:8038 tk4: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 DASE 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/tk4/dasd.usr/usr_dasd.cnf to automatically attach the newly created dasd at address 34a. This file is referenced as include in the TK4- base configuration file (/opt/tk4/conf/tk4-.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 ```","has_starred","hub_user","immutable_tags_settings",{"_75":11,"_76":77},"enabled","rules",[78],".*","is_automated","permissions",{"_82":22,"_83":11,"_84":11},"read","write","admin","user","storage_size",2947445528,"orgData","recentTags",[91,130],{"_92":44,"_93":94,"_95":96,"_97":98,"_99":100,"_101":102,"_50":119,"_120":94,"_121":33,"_122":56,"_57":123,"_124":125,"_126":109,"_127":119,"_128":66,"_129":22},"content_type","creator",4550052,"digest","sha256:8e14e91fa83fc4147422925646c59d21a3ffc6b989e1c38be6c7d24075742bc4","full_size",469844447,"id",435110472,"images",[103],{"_104":105,"_95":96,"_106":107,"_108":109,"_110":111,"_112":113,"_114":107,"_115":-5,"_116":98,"_63":66,"_117":118},"architecture","arm64","features","","last_pulled","2026-11-01T16:50:05.072069003Z","last_pushed","2023-05-07T15:38:31Z","os","linux","os_features","os_version","size","variant","v8","2023-05-07T15:38:30.682376Z","last_updater","last_updater_username","media_type","latest","repository",19675561,"tag_last_pulled","tag_last_pushed","tag_status","v2",{"_92":44,"_93":94,"_95":131,"_97":132,"_99":133,"_101":134,"_50":138,"_120":94,"_121":33,"_122":56,"_57":139,"_124":125,"_126":136,"_127":138,"_128":66,"_129":22},"sha256:ebf4b84aa1e165c024c9c88c85778c7c4c0d4ba64a5113135f3e395b4bd028bc",620687345,435111435,[135],{"_104":105,"_95":131,"_106":107,"_108":136,"_110":137,"_112":113,"_114":107,"_115":-5,"_116":132,"_63":66,"_117":118},"2026-10-20T09:17:27.660722462Z","2023-05-07T15:43:24Z","2023-05-07T15:43:23.249416Z","rob","sbxKitMetadata","isPotentialSpam","isHubSbxKitsEnabled","showSbxRunInCloud","showSbxLogoOverride","sbxTrademarkText","displaySecurityMetadata","tagAttestations","tagsHaveAttestations",[],"selectedTag","attestationsUrl","routes/_layout.r.$namespace.$reponame.tags",{"_38":154,"_161":162,"_148":175,"_176":11},{"_40":155,"_42":156,"_45":46,"_47":48,"_49":11,"_50":51,"_52":53,"_54":157,"_57":35,"_32":33,"_58":59,"_60":44,"_61":62,"_63":64,"_65":66,"_67":-5,"_68":62,"_69":70,"_71":11,"_72":33,"_73":158,"_79":11,"_80":160,"_85":33,"_86":87},[],[44],[56],{"_75":11,"_76":159},[78],{"_82":22,"_83":11,"_84":11},"tags",{"_163":164,"_165":-5,"_166":-5,"_167":168},"count",2,"next","previous","results",[169,172],{"_92":44,"_93":94,"_95":131,"_97":132,"_99":133,"_101":170,"_50":138,"_120":94,"_121":33,"_122":56,"_57":139,"_124":125,"_126":136,"_127":138,"_128":66,"_129":22},[171],{"_104":105,"_95":131,"_106":107,"_108":136,"_110":137,"_112":113,"_114":107,"_115":-5,"_116":132,"_63":66,"_117":118},{"_92":44,"_93":94,"_95":96,"_97":98,"_99":100,"_101":173,"_50":119,"_120":94,"_121":33,"_122":56,"_57":123,"_124":125,"_126":109,"_127":119,"_128":66,"_129":22},[174],{"_104":105,"_95":96,"_106":107,"_108":109,"_110":111,"_112":113,"_114":107,"_115":-5,"_116":98,"_63":66,"_117":118},[],"canDeleteTags","actionData","errors"]

praths/tk4

Tags for praths/tk4