Ap Tuner 3.08 Serial Number
pergrebinseThis page describes the configuration file for the Hercules S/370,ESA/390, and z/Architecture emulator.The configuration file
hercules.cnf contains theprocessor and device layout. It is roughly equivalent to the IOCDS ona real System/390. The configuration file is an ASCII text file.Example configuration filePlease note that the below example configuration file should notbe considered a good example of what an actual configuration filelooks like. It is only meant to illustrate what someof the supported configuration file statements look likeand how they are used.#################################################################### # HERCULES EMULATOR CONTROL FILE # # (Note: not all parameters are shown) # #################################################################### # # System parameters # ARCHMODE ESA/390 OSTAILOR OS/390 LOADPARM 0120.... CPUSERIAL 000611 CPUMODEL 3090 CPUVERID FD LPARNAME HERCULES LPARNUM 21 MODEL EMULATOR PLANT ZZ MANUFACTURER HRC MAINSIZE 64 XPNDSIZE 0 NUMCPU 1 NUMVEC 1 MAXCPU 8 ENGINES CP SYSEPOCH 1900 YROFFSET -28 TZOFFSET -0500 HTTPROOT /usr/local/share/hercules/ HTTPPORT 8081 NOAUTH CCKD RA=2,RAQ=4,RAT=2,WR=2,GCINT=10,GCPARM=0,NOSTRESS=0,TRACE=0,FREEPEND=-1 SHRDPORT 3990 PANTITLE "My own private MAINFRAME!" PANRATE FAST LOGOPT TIMESTAMP CODEPAGE default CNSLPORT 3270 CONKPALV (3,1,10) LEGACYSENSEID OFF HERCPRIO 0 TODPRIO -20 DEVPRIO 8 CPUPRIO 15 TIMERINT DEFAULT TODDRAG 1.0 DEVTMAX 8 DIAG8CMD disable SHCMDOPT disable DEFSYM TAPEDIR "$(HOME)/tapes" AUTOMOUNT $(TAPEDIR) AUTOMOUNT +/tapes AUTOMOUNT -/tapes/vault MODPATH /usr/local/hercules LDMOD dyncrypt PGMPRDOS restricted ECPSVM no ASN_AND_LX_REUSE disable AUTO_SCSI_MOUNT no MOUNTED_TAPE_REINIT allow INCLUDE mydevs.cfg IGNORE INCLUDE_ERRORS INCLUDE optdevs.cfg # # Device statements # 0009 3215-C / 000A 1442 adrdmprs.rdr 000C 3505 jcl.txt ascii trunc 000D 3525 pch00d.txt ascii 000E 1403 prt00e.txt noclear 001E 1403 192.168.200.1:1403 sockdev 001F 3270 * 192.168.0.1 0200.4 3270 * 192.168.0.0 255.255.255.0 0220.8 3270 GROUP1 192.168.100.0 255.255.255.0 0228.8 3270 GROUP2 0230.16 3270 0000 SYSG SYSGCONS 0120 3380 $DASD_PATH=dasd/mvsv5r.120 0121 3380 $DASD_PATH=dasd/mvsv5d.121 0122 3380 $DASD_PATH=dasd/mvswk1.122 0123 3380 192.168.1.100 0140 3370 dosres.140 0141 3370 syswk1.141 0300 3370 sysres.300 0400 CTCT 30880 192.168.100.2 30880 2048 0401 CTCT 30881 192.168.100.2 30881 2048 0420.2 CTCI 192.168.200.1 192.168.200.2 0440.2 LCS -n /dev/net/tun 192.168.200.2 0E40 CTCE 31880 192.168.1.202 32880 0E41 CTCE 31882 192.168.1.202 32882 0580 3420 /dev/nst0 # SCSI (Linux or Windows) 0581 3420 \\.\Tape0 # SCSI (Windows only) 0582 3420 ickdsf.aws noautomount 0583 3420 /cdrom/tapes/uaa196.tdf 0584-0587 3420 $(TAPEDIR)/volumes.$(CUU) maxsizeM=170 eotmargin=131072 0590 3480 /dev/nst0 --no-erg --blkid-32 # Quantum DLT SCSI 0023 2703 lport=3780 rhost=localhost rport=3781 dial=no 00C3 2703 lport=32003 dial=IN tty=1Comment lines Blank lines, and lines beginning with a # sign or an asterisk, are treated as comments. System parameters System parameters may appear in any order but they must precede all device statements. Each system parameter must be on a separate line. The following system parameters may be specified:ARCHMODE S/370 ESA/390 z/Arch ESAME specifies the initial architecture mode: use S/370 for OS/360, VM/370, and MVS 3.8. use ESA/390 for MVS/XA, MVS/ESA, OS/390, VM/ESA, VSE/ESA, Linux/390, and ZZSA. use z/Arch or ESAME for z/OS and zLinux. ESAME is a synonym for z/Arch. When z/Arch or ESAME is specified, the machine will always IPL in ESA/390 mode, but is capable of being switched into z/Architecture mode after IPL. This is handled automatically by all z/Architecture operating systems. ASN_AND_LX_REUSE DISABLE ENABLE specifies that the ASN-and-LX-Reuse Facility (ALRF) is to be disabled or enabled. The default is disabled. This is a z/Architecture-only feature (it is always disabled for S/390 or ESA/390). Set this to ENABLE if the operating system supports this z/Architecture feature and the use of this feature is desired. Set it to DISABLE or do not specify anything if the operating system doesn't support this feature, and it inadvertently sets CR0 bit 44 to 1, usually leading to unexpected program interrupt when instructions such as LASP are issued. ASN_AND_LX_REUSE may be abbreviated as ALRF AUTOMOUNT []directory specifies the host system directory where the guest is allowed or not allowed to automatically load virtual tape volumes from. Prefix allowable directories with a '+' plus sign and unallowable directories with a '-' minus sign. The default prefix if neither is specified is the '+' plus sign (i.e. an allowable directory).
Caution: Enabling this feature may have security consequences depending on which allowable host system directories you specify as well as how your guest operating system enforces authorized use of the Set Diagnose (X'4B') channel command code. All host system virtual tape volumes to be "automounted" by the guest must reside within one of the specified allowable host system directories or any of its subdirectories while not also being within any of the specified unallowable directories or any of their subdirectories, in order for the guest-invoked automount to be accepted. Note: specifying a disallowed automount directory does not preclude the Hercules operator from manually mounting any desired file via the devinit panel command -- even one in a currently defined "disallowed" automount directory. The AUTOMOUNT statement only controls guest-invoked automatic tape mounts and not manual tape mounts performed by the Hercules operator. All directories must be specified on separate statements, but as many statements as needed may be specified in order to describe the desired allowable/unallowable directories layout. For convenience, an automount panel command is also provided to dynamically add/remove new/existing allowable/unallowable automount directories at any time. The automount feature is activated whenever you specify at least one allowable or unallowable directory. If only unallowable directories are specified, then the current directory becomes the only defined allowable automount directory by default. All specified directories are always resolved to fully-qualified absolute directory paths before being saved. Refer to the description of the virtual tape device 'noautomount' option for more information. AUTO_SCSI_MOUNT NO YES nn specifies whether automatic detection of SCSI tape mounts are to be enabled or not. Specifying NO or 0 seconds (the default) indicates the option is disabled, forcing all SCSI tape mounts to be done manually via an appropriate devinit command. A value from 1 to 99 seconds inclusive enables the option and causes periodic queries of the SCSI tape drive to automatically detect when a new tape is mounted. Specifying YES is the same as specifying 5 seconds, the current default interval. The scsimount panel command may also be used to display and/or modify this value on demand once Hercules has been started. Note too that the scsimount panel command also lists any mounts and/or dismounts that may still be pending on the drive, as long as you've defined your tape drive as a model that has an LCD "display" (such as a model 3480, 3490 or 3590). Note: enabling this option may cause Hercules to take longer to shutdown depending on the value specified for this option as well as how the host operating system (Windows, Linux, etc) and associated hardware (SCSI adapter) behaves to drive status queries for drives which do not have any media currently mounted on them. CCKD cckd-parameters The CCKD command and initialization statement can be used to affect cckd processing. The CCKD initialization statement is specified as a Hercules configuration file statement and supports the same options as the cckd panel command. Refer to the Compressed Dasd Emulation web page for more information. CODEPAGE mapping specifies the codepage conversion mapping table used for ASCII/EBCDIC translation. default specifies traditional Hercules codepage mapping. Other supported codepage mappings are: Mapping Description ASCII EBCDIC 437/037 437 PC United States 037 United States/Canada 437/500 437 PC United States 500 International 437/1047 437 PC United States 1047 Open Systems Latin 1 819/037 819 ISO-8859-1 037 United States/Canada 819/037v2 819 ISO-8859-1 037 United States/Canada version 2 819/273 819 ISO-8859-1 273 Austria/Germany 819/277 819 ISO-8859-1 277 Denmark/Norway 819/278 819 ISO-8859-1 278 Finland/Sweden 819/280 819 ISO-8859-1 280 Italy 819/284 819 ISO-8859-1 284 Spain 819/285 819 ISO-8859-1 285 United Kingdom 819/297 819 ISO-8859-1 297 France 819/500 819 ISO-8859-1 500 International 819/1047 819 ISO-8859-1 1047 Open Systems Latin 1 850/273 850 PC Latin 1 273 Austria/Germany 850/1047 850 PC Latin 1 1047 Open Systems Latin 1 1252/037 1252 Windows Latin 1 037 United States/Canada 1252/037v2 1252 Windows Latin 1 037 United States/Canada version 2 1252/1047 1252 Windows Latin 1 1047 Open Systems Latin 1 1252/1140 1252 Windows Latin 1 1140 United States/Canada with Euro Iconv single byte codepages may also be used (e.g. UTF8/EBCDIC-CP-NL) if the host environment supports iconv. If no codepage is specified then the environment variable HERCULES_CP will be inspected. The default codepage mapping is default. CNSLPORT nnnn specifies the port number (in decimal) to which tn3270 and telnet clients will connect. The CNSLPORT statement may also have the form of host:port, where the telnet console server will bind to the specified address. CONKPALV (idle,intv,count) specifies the tn3270 console and telnet clients keep-alive option values that control automatic detection of disconnected tn3270/telnet client sessions. idle specifies the number of seconds of inactivity until the first keep-alive probe is sent (idle time until first probe, or probe frequency).intv specifies the interval in seconds between when successive keep-alive packets are sent if no acknowledgement is received from the previous one (i.e. the timeout value of the probes themselves).
count specifies the number of unacknowledged keep-alive packets sent before the connection is considered to have failed. The default values are 3, 1, and 10. That is, send the initial probe 3 seconds after the line goes idle and then wait no more than one second for it to be responded to. Do this 10 times before considering the client as having died.
Note: This is a built-in feature of TCP/IP and allows detection of unresponsive TCP/IP connections and not idle clients. That is to say, your connection will not be terminated after 3 seconds of idle time. Your 3270 session can remain idle for many minutes without any data being transmitted. If the TCP/IP stack at the other end of the connection -- not your 3270 client itself -- fails to respond to the internal keep-alive probe packets, then it means that the TCP/IP stack is down or there has been a break in the connection. Thus, even if your 3270 client is completely idle, your system's TCP/IP stack itself should still respond to the keep-alive probes sent by the TCP/IP stack at the Hercules end of the link. If it doesn't, then TCP/IP will terminate the tn3270/telnet session which will cause Hercules to disconnect the terminal. The three values can also be modified on-demand via the conkpalv panel command, which has the exact same syntax. Note that the syntax is very unforgiving: no spaces are allowed anywhere within the parentheses and each value must be separated from the other with a single comma. Note: On Windows platforms the count value is ignored and cannot be changed from its default value of 10. Also, some older platforms may ignore all of the values specified and use platform default values instead. CPUMODEL xxxx specifies the 4 hexadecimal digit CPU machine type number stored by the STIDP instruction Note: Prior to ESA/390 this was known as the CPU model number CPUPRIO nn specifies the priority of the CPU thread. Default is a nice value of 15, which means a low priority such that I/O can be scheduled and completed in favour of CPU cycles being burned. On Multi-CPU systems, a real CPU can be "dedicated" to Hercules, by giving the CPU thread a very high dispatching priority (-20). See "Thread Priorities" below for more information. Caution: CPUPRIO should not have a higher dispatching priority than the TOD Clock and timer thread. CPUSERIAL xxxxxx specifies the 6 hexadecimal digit CPU serial number stored by the STIDP instruction CPUVERID xx specifies the 2 hexadecimal digit CPU version code stored by the STIDP instruction. The default version code is FD when ARCHMODE S/370 or ARCHMODE ESA/390 is specified. For the z/Architecture mode, the version code is always stored as 00 and the value specified here is ignored. DEFSYM symbol value Defines symbol symbol as to contain value value. The symbol can then be the object of a substitution later in the configuration file or for panel commands. If value contains blanks or spaces, then it should be enclosed in double quotation marks ("). See substitutions for a more in-depth discussion on this feature. Substitution is available even in configuration statements, meaning it is possible to perform substitution in the DEFSYM statement itself. However, symbols are always defined as the last step in the process, so attempting to self define a symbol will result in an empty string: DEFSYM FOO $(FOO) Will set symbol FOO to "" DEVPRIO nn specifies the priority of the device threads. The default value is 8. See "Thread Priorities" below for more information. Caution: DEVPRIO should not have a higher dispatching priority than the TOD Clock and timer thread. DEVTMAX -1 0 nnn specifies the maximum number of device threads allowed. Specify -1 to cause 'one time only' temporary threads to be created to service each I/O request to a device. Once the I/O request is complete, the thread exits. Subsequent I/O to the same device will cause another worker thread to be created again. Specify 0 to cause an unlimited number of 'semi-permanent' threads to be created on an 'as-needed' basis. With this option, a thread is created to service an I/O request for a device if one doesn't already exist, but once the I/O is complete, the thread enters an idle state waiting for new work. If a new I/O request for the device arrives before the timeout period expires, the existing thread will be reused. The timeout value is currently hard coded at 5 minutes. Note that this option can cause one thread (or possibly more) to be created for each device defined in your configuration. Specifying 0 means there is no limit to the number of threads that can be created. Specify a value from 1 to nnn to set an upper limit to the number of threads that can be created to service any I/O request to any device. Like the 0 option, each thread, once done servicing an I/O request, enters an idle state. If a new request arrives before the timeout period expires, the thread is reused. If all threads are busy when a new I/O request arrives however, a new thread is created only if the specified maximum has not yet been reached. If the specified maximum number of threads has already been reached, then the I/O request is placed in a queue and will be serviced by the first available thread (i.e. by whichever thread becomes idle first). This option was created to address a threading issue (possibly related to the cygwin Pthreads implementation) on Windows systems. The default for Windows is 8. The default for all other systems is 0. DIAG8CMD DISABLE ENABLE [ECHO NOECHO] When ENABLE is specified, commands issued through the Diagnose 8 interface will be executed by Hercules as Hercules commands. When set to DISABLE, commands issued through the Diagnose 8 interface will generate a Specification Exception program interrupt on the issuing CPU. An optional second argument can be given to request whether the commands issued using the Diagnose 8 interface will be traced at the console. This may be useful for programs that routinely issue panel commands using the Diagnose 8 interface. When ECHO is specified, a message is issued as the panel is about to issue the command, the command is redisplayed as if it was entered through the panel input line, and a final message is issued to indicate the command completed. When NOECHO is specified, no such messages are displayed and the command completes silently. The value of ECHO or NOECHO has no effect on command output being placed into a response buffer if the Diagnose 8 interface requested one. The default is DISABLE NOECHO Caution: Enabling this feature may have security consequences. When this feature is enabled it is possible for guest operating systems running under Hercules to issue commands directly to the host operating system by means of the Hercules sh (shell) command. This ability may be disabled via the SHCMDOPT statement. ECPSVM YES NO LEVEL nn specifies whether ECPS:VM (Extended Control Program Support : Virtual Machine) support is to be enabled. If YES is specified, then the support level reported to the operating system is 20. The purpose of ECPS:VM is to provide to the VM/370 Operating system a set of shortcut facilities to perform hypervisor functions (CP Assists) and virtual machine simulation (VM Assists). Although this feature does not affect VM Operating system products operating in XA, ESA or z/Architecture mode, it will affect VM/370 and VM/SP products running under VM/XA, VM/ESA or z/VM. Running VM/370 and VM/SP products under VM/XA, VM/ESA or z/VM should be done with ECPS:VM disabled. ECPS:VM should not be enabled in an AP or MP environment. ECPS:VM has no effect on non-VM operating systems. It is however recommended to disable ECPS:VM when running native non-VM operating systems. If a specific LEVEL is specified, this value will be reported to the operating system when it issues a Store ECPS:VM level, but it doesn't otherwise alter the ECPS:VM facility operations. This is a partial implementation. ENGINES [nn*]CPILAPIP[,...] specifies the type of engine for each installed processor. The default engine type is CP. nn* is an optional repeat count. Spaces are not permitted. Examples: ENGINES CP,CP,AP,IPspecifies that processor engines 0 and 1 are of type CP, engine 2 is type AP, and engine 3 is type IP. ENGINES 4*CP,2*AP,2*IP
specifies that the first four processor engines (engines 0-3) are of type CP, the next two (engines 4-5) are of type AP, and the next two (engines 6-7) are of type IP. The number of installed processor engines is determined by the MAXCPU statement. If the ENGINES statement specifies more than MAXCPU engines, the excess engines are ignored. If fewer than MAXCPU engines are specified, the remaining engines are set to type CP. HERCPRIO nn specifies the process priority for Hercules. The default is 0. See "Process Priorities" below for more information. HTTPPORT nnnn [AUTH NOAUTH] [ userid password ] specifies the port number (in decimal) on which the HTTP server will listen. The port number must either be 80 or within the range 1024 - 65535 inclusive. If no HTTPPORT statement is present or an invalid port number is specified, then the HTTP server thread will not be activated.
AUTH indictates that a userid and password are required to access the HTTP server, whereas NOAUTH indicates that a userid and password are not required. The userid and password may be any valid string. HTTPROOT directory specifies the root directory where the HTTP server's files reside. If not specified, the default value for Win32 builds of Hercules is the directory where the Hercules executable itself is executing out of, and for