RE: [hercules-390] Newbie Question - CCW Trace Messages on Console - 3.07
"Fish" (David B. Trout)
> Hi All:
>
> I upgraded to 3.07 last week and note that there is some
> tracing on for certain devices by default:
[...]
> 000c is my card reader, 00c0-00c2 are my TSO 3270s.
>
> The messages occur on startup and thereafter whenever the
> specified devices are accessed.
[...]
> Any suggestions on how to turn them off?
Yes: make sure all of the devices in question are available when you IPL you
guest. :)
In other words, change your 00C device statement to be:
000C 3505 cards.txt
(where 'cards.txt' is an empty file that actually exists on your host (e.g.
Windows, Linux, etc)).
For devices 00C0 - 00C2, make sure you connect a TN3270 session to Hercules
before you IPL your guest.
For devices 0310 and 0311, use:
0310 3420 tape310.het
0311 3420 tape311.het
(where 'tape310.het' and 'tape311.het' are emulated tape files created via
hetinit.)
Do all that and the messages SHOULD go away.
The bottom line is this: Hercules issues the messages you mention whenever
an i/o error occurs, and in your case an i/o DID occur! Because the devices
were defined in your Hercules configuration file, your guest (MVS) attempted
to do i/o to those devices, but encountered an error. The "error" it
encountered was simply "intervention required" (i.e. "the device is not
ready").
This is completely normal whenever a device "exists" (in your configuration)
but is not otherwise "ready". Defining TSO terminals for example (0c0-0c2)
but then not actually connecting a TSO session to Hercules before you IPL
will cause the message to occur every time.
Defining a tape drive in your configuration but not having any tape (media)
mounted on it will also cause the message to occur.
Same with your card reader, etc.
All of this is completely normal and nothing to worry about.
And as I said, there's really no way to suppress the messages either, short
of doing what I suggested above (i.e. ensuring each device is available and
ready before IPLing your guest).
Hope that helps!
--
"Fish" (David B. Trout)
fi...@softdevlabs.com
------------------------------------
Community email addresses:
Post message: hercul...@yahoogroups.com
Subscribe: hercules-39...@yahoogroups.com
Unsubscribe: hercules-390...@yahoogroups.com
List owner: hercules-...@yahoogroups.com
Files and archives at:
http://groups.yahoo.com/group/hercules-390
Get the latest version of Hercules from:
http://www.hercules-390.org
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/hercules-390/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/hercules-390/join
(Yahoo! ID required)
<*> To change settings via email:
hercules-...@yahoogroups.com
hercules-390...@yahoogroups.com
<*> To unsubscribe from this group, send an email to:
hercules-390...@yahoogroups.com
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
"Fish" (David B. Trout)
[...]
> Incidentally we are getting attacked by the first blizzard
> of the season. Vanya you're not at fault here, neither is
> the one who types with fins.
<me: typing with my fins...>
Stay warm, Greg!
Don't venture out unless you absolutely need to.
Rather, make a cup of hot chocolate and sit by the fire instead. :)
somitcw
--- In hercul...@yahoogroups.com,
Kevin McQuiggin <mcquiggi@...> wrote:
>> From: Kevin McQuiggin <mcquiggi@...>
>> Date: December 26, 2010 6:19:06 PM PST
>> To: hercul...@yahoogroups.com
>> Subject: Re: [hercules-390] Newbie Question -
>>CCW Trace Messages on Console - 3.07
>> H Gerhard:
>> Thank you for the reply. Here is my mvs.cnf:
>> #
>> # Configuration file for Hercules ESA/390 emulator
>> #
>> # use for running the target MVS 3.8j system
>> # (last modified for use with Hercules 3.05 on 17 Feb 2008)
>> #
>> ARCHMODE S/370
>> CPUSERIAL 000611
>> CPUMODEL 0148
>> MAINSIZE 32
Only 16 is used by MVS 3.8j unless you are testing
or playing with real memory addresses greater than 16MB.
I use MAINSIZE 160 for my playing
>> XPNDSIZE 0
>> CNSLPORT 3270
>> NUMCPU 1
>> LOADPARM ........
>> SYSEPOCH 1960
"Use 1960 for OS/360." but you are running OS/370.
With SYSEPOCH 1960, don't expect current dates.
There are a couple of TSO zaps to replace hard-coded
'19' with hard-coded '20' but they aren't required.
>> TZOFFSET -0300
This tells MVS that GMT/UTC time and local time
are the same time. It may be better to be more
accurate and use SYS1.PARMLIB(PARMTZ) for local time.
Yahoo or Google search for PARMTZ should give details.
>> PANRATE 250
>> # .-----------------------------Device number
>> # | .-----------------------Device type
>> # | | .---------------File name
>> # | | |
>> # V V V
>> #--- ---- --------------------
>> 000C 3505
File name is missing. Things like that could
prevent JES2 from shutting down properly if JES2
is trying to use 000C.
I have a C:\MVS\jcl\dummy that contains:
//DUMMY JOB DUMMY,DUMMY
//DUMMY EXEC PGM=IEFBR14
//
My Hercules configuration file has:
000C 3505 jcl\dummy ascii trunc eof
I don't remember if it was part of MVS Tur(n)key #3
or a later addition but since you went another route,
you may not have jcl\dummy or a file like it?
I also removed $SRDR1 from JES2PARM member of
SYS1.JES2PARM and SYS1.PARMLIB so wouldn't get any
messages about 000C anyway. If I would ever need
000C to be a JES2 reader, I would issue the command
manually. As in actually type in /$SRDR1 followed
by /$PRDR1
>> # ------------------------------------------- 3420 on channel 3
>> 0310 3420 *
>> 0311 3420 *
>> # ------------------------------------------- punch & printers
>> 000D 3525 pch00d.txt ascii
>> 000E 1403 prt00e.txt
>> 000F 3211 prt00f.txt
>> # ------------------------------------------- 3330 on channel 1
>> 0130 3330 dasd/work01.152
>> # ------------------------------------------- 3350 on Channel 1
>> 0150 3350 dasd/mvsres.3350
>> 0151 3350 dasd/smp001.3350
>> 0152 3350 dasd/work02.3350
>> 0153 3350 dasd/kev001.3350
>> # ------------------------------------------- 3380 on Channel 1
>> # ------------------------------------------- 3330 on Channel 2
>> # ------------------------------------------- 3350 on Channel 2
>> 0250 3350 dasd/page00.3350
>> 0251 3350 dasd/spool1.3350
>> 0257 3350 dasd/syscpk.3350
>> # ------------------------------------------- 3380 on Channel 2
>> # ------------------------------------------- 2314 on Channel 1
>> # ------------------------------------------- consoles
>> 0010 3270 console
Apparently the control unit doesn't respond as
expected if the CRT device is not powered-up/connected.
I don't know if that matches real CRTs, but it functions.
>> #0011 3270 altconsole
>> 0012 1403 mvslog.txt
If you don't need CRT consoles and telnet consoles,
or just want another version of the console log,
depending on your consoles, you may want to add:
0009 3215-c / noprompt
or
001F 3215-c / noprompt
but don't do both with the same command character "/".
Some, like "#" and ".", are "reserved" for other uses.
That way no CRT or telnet consoles need to be
attached for IPL. CRT and telnet consoles are not
required for anything else other than your wish to
use or play with them.
To find your console addresses and types, use MVS
commands like "D C", "D C,L", "D U,,,009,7", etc. or
check your STAGE1 source.
>> # ------------------------------------------- 3270's
>> 00C0.3 3270 tso
Apparently the control unit doesn't respond as
expected if the CRT device is not powered-up/connected.
I don't know if that matches real CRTs, but it functions.
>> Only minor changes from Jay Moseley's base version.
>> Kevin
>> On 2010-12-26, at 2:54 PM, Gerhard Postpischil wrote:
>>> On 12/26/2010 2:40 PM, mcquiggi wrote:
>>>> Hi All:
>>>> I upgraded to 3.07 last week and note that there
>>>>is some tracing on for certain devices by default:
>>>> HHCCP076I 000C:Sense=40100000 00000000 00000000
>>>>00000000 00000000 00000000
>>> I've been running 3.07 for several months, and don't
>>>see that. Perhaps you could post your .rc and .conf
>>>files to see whether there's anything problematic in
>>>there?
>>> Gerhard Postpischil
>>> Bradford, VT
> [Non-text portions of this message have been removed]
Post message: hercul...@yahoogroups.com
Subscribe: hercules-39...@yahoogroups.com
Unsubscribe: hercules-390...@yahoogroups.com
List owner: hercules-...@yahoogroups.com
Files and archives at:
http://groups.yahoo.com/group/hercules-390
Get the latest version of Hercules from:
http://www.hercules-390.org
somitcw
--- In hercul...@yahoogroups.com,
Gerhard Postpischil <gerhard@...> wrote:
> On 12/26/2010 6:38 PM, Gregg Levine wrote:
>> Gerhard, I sometimes see similar traffic when running
>>VM/370rel6 on Hercules 3.07. (Slackware build)
> Fish explained it adequately, although I question the
>decision by the developers, purportedly so fussy about
>adhering to real iron standards, doing something
>non-prototypical <g>
> On my machines I used the IPL option of varying not-ready
>DASD and tape off-line, but the machine never issued any
>messages!
I suspect that the 000C problem is a hidden $SRDR1
in the system trying to read cards. Hercules is just
giving useful informational messages.
The CRT messages are strange but not causing harm.
>> Incidentally we are getting attacked by the first
>>blizzard of the season. Vanya you're not at fault here,
>>neither is the one who types with fins.
> So far there's about 4-6" on the ground here, and it's
>still going. I live in this weird place where, most of
>the time, the bad weather is always somewhere else.
> Gerhard Postpischil
> Bradford, VT
My part of Richmond Virginia got the same 4 to 6
inches but it ended last night sometime.
Ignoring Al Gore, last, this, and next winter should
be cold because of the sun spot cycles.
Post message: hercul...@yahoogroups.com
Subscribe: hercules-39...@yahoogroups.com
Unsubscribe: hercules-390...@yahoogroups.com
List owner: hercules-...@yahoogroups.com
Files and archives at:
http://groups.yahoo.com/group/hercules-390
Get the latest version of Hercules from:
http://www.hercules-390.org
somitcw
--- In hercul...@yahoogroups.com,
Kevin McQuiggin <mcquiggi@...> wrote:
> On 2010-12-26, at 8:58 PM, Gerhard Postpischil wrote:
>> On 12/26/2010 9:20 PM, Kevin McQuiggin wrote:
>>>> Thank you for the reply. Here is my mvs.cnf:
>> I don't see anything in there that could cause
>>your symptoms. So I hope somebody else has an idea?
>> I did note some other stuff that's irrelevant, but
>>not necessary:
>>>> MAINSIZE 32
>> MVS is limited to 16MB. MVS/SP used up to 64K, but
>>I'm not aware of that version being available.
>>>> LOADPARM ........
>> Doesn't do anything for 370 mode.
>>>> SYSEPOCH 1960
>> Looks funny (I run without), but fine if your system
>>dates work. But then I run the system derived from
>>the turnkey, not Jay's version.
>> Gerhard Postpischil
>> Bradford, VT
> Thanks Gerhard:
> The combination of SYSEPOCH and timezone in my .cnf
>file gives me accurate date and time, except for the
>year being seen as 1950.
> Regarding my choice of time zone, I am actually at
>UTC-8 hrs (Pacific standard time), but -0800 for the
>time zone parameter left me 5 hours behind the current
>time; hence -0300 seems to work. My system clock is
>set to UTC. I am not sure why -0800 didn't work but
>will eventually (probably) understand why it didn't.
> Any insight as to why -0800 doesn't work?
> Kevin
> [Non-text portions of this message have been removed]
SYS1.PARMLIB(PARMTZ) W,05 for U.S. Eastern Standard
time plus Hercules configuration file -0300 should be
W,08 so you should have the correct "local" time.
You should expect an MVS /D T to look weird.
As for why you want 1960 for a base date? It is your
system so use whatever you want.
Post message: hercul...@yahoogroups.com
Subscribe: hercules-39...@yahoogroups.com
Unsubscribe: hercules-390...@yahoogroups.com
List owner: hercules-...@yahoogroups.com
Files and archives at:
http://groups.yahoo.com/group/hercules-390
Get the latest version of Hercules from:
http://www.hercules-390.org
