Old virtual 3390 volumes

[a***@public.gmane.org]

Hello all,

I still have some backup copies of my old virtual 3390 volumes.
These files originated from my P390, which is not currently
available to me.

I just wondered whether I might use Hercules to access these
volumes to extract some source files that are on those old 3390s.
Any chance hercules can do that - or does it use an entirely
different internal structure for its virtual 3390 devices?

Thanks in advance,
Abe Kornelis.
=========

[au1john]

Post by a***@public.gmane.org
Hello all,
I still have some backup copies of my old virtual 3390 volumes.
These files originated from my P390, which is not currently
available to me.
I just wondered whether I might use Hercules to access these
volumes to extract some source files that are on those old 3390s.
Any chance hercules can do that - or does it use an entirely
different internal structure for its virtual 3390 devices?

The first obvious question.. in what format are these "backup copies"?

Post by a***@public.gmane.org
Thanks in advance,
Abe Kornelis.
=========

[a***@public.gmane.org]

I thought it was obvious, but obviously
that ain't so. They are just plain copies
of the original file.

More specifically, I used to zip the files
for backup purposes, then zip the resulting
zip file. Very efficient in terms of storage,
which was a major concern as I had only
diskettes as a backup medium. (Yes, I am
that old, already).

Returning to the 3390 volumes - as they are
verbatim copies of the original OS2-supported
virtual 3390 volumes, I thought/hoped that
I might be able to install Hercules, and
then mount these files to as virtual 3390s
to the Hercules system.

Come to think of it, those old 3390s were
not complete 3390-9 volumes; they had fewer
cylinders to make the virtual volume fit
within a single physical file. Larger volumes
were supported using two files.

Cheers,
Abe.
===





----- Original Message -----
From: au1john
To: hercules-390-***@public.gmane.org
Sent: Wednesday, January 02, 2008 9:20 AM
Subject: [hercules-390] Re: Old virtual 3390 volumes

Post by a***@public.gmane.org
Hello all,
I still have some backup copies of my old virtual 3390 volumes.
These files originated from my P390, which is not currently
available to me.
I just wondered whether I might use Hercules to access these
volumes to extract some source files that are on those old 3390s.
Any chance hercules can do that - or does it use an entirely
different internal structure for its virtual 3390 devices?

The first obvious question.. in what format are these "backup copies"?

Post by a***@public.gmane.org
Thanks in advance,
Abe Kornelis.
=========

[Non-text portions of this message have been removed]

[Rob van der Heij]

Post by a***@public.gmane.org
I thought it was obvious, but obviously
that ain't so. They are just plain copies
of the original file.

Would it not "just work" out of the box once you have unzipped the files?

http://www.hercules-390.org/hercload.html mentions specifically that
you can use the ADCD and DemoPKG images, and from what I recall those
were just the P/390 image files. I think Hercules will do the _2 trick
as well for the part of the disk above 2GB

Rob

[a***@public.gmane.org]

Rob,

Would it not "just work" out of the box once you have unzipped the files?
**--> Probably. I wanted to verify before starting to install Hercules.
I tried to do that a few years ago, and miserably failed to get it
working. Given enough time it should be feasible, of course.
But time is indeed a major constraint to me.

http://www.hercules-390.org/hercload.html mentions specifically that
you can use the ADCD and DemoPKG images, and from what I recall those
were just the P/390 image files. I think Hercules will do the _2 trick
as well for the part of the disk above 2GB

**--> Thanks for your reply.

Abe.
===

[Gerhard Postpischil]

Post by Rob van der Heij
Would it not "just work" out of the box once you have unzipped the files?
**--> Probably. I wanted to verify before starting to install Hercules.
I tried to do that a few years ago, and miserably failed to get it
working. Given enough time it should be feasible, of course.
But time is indeed a major constraint to me.

One aspect I have not seen mentioned, even though it's buried in
the archives somewhere, is that not all MVS utilities support
3380 and 3390 drives, most notably IEBCOPY compress.

When I moved my programs from the P/390, I used ftp to transfer
the disk images, then defined them ReadOnly, with shadow files,
then copied the source to 3350s. I didn't bother with load
module libraries, as everything needed to be assembled for MVS
anyway.

Gerhard Postpischil
Bradford, VT

[au1john]

Post by a***@public.gmane.org
I thought it was obvious, but obviously
that ain't so. They are just plain copies
of the original file.

And the original file was in what format?

Post by a***@public.gmane.org
More specifically, I used to zip the files
for backup purposes, then zip the resulting
zip file. Very efficient in terms of storage,
which was a major concern as I had only
diskettes as a backup medium. (Yes, I am
that old, already).

Age!! Shit, I've used 8" floppies.

Post by a***@public.gmane.org
Returning to the 3390 volumes - as they are
verbatim copies of the original OS2-supported
virtual 3390 volumes, I thought/hoped that
I might be able to install Hercules, and
then mount these files to as virtual 3390s
to the Hercules system.

Why not just try it? To me the costs to you seem to be time and
bandwidth.

Whilst I don't know all the details for certain, Herc does seem to
have been built around the emulated file systems used for the P390.
Certainly the .aws format is supported for tape emulation. Somewhere
in the back of my mind is a suspicion that DASD emulation was also of
a .aws form. I could be way wrong here though.

Post by a***@public.gmane.org
Come to think of it, those old 3390s were
not complete 3390-9 volumes; they had fewer
cylinders to make the virtual volume fit
within a single physical file. Larger volumes
were supported using two files.

If Herc does support the disk format the 3390 images you have, then
the OS you are running under Herc also needs to support 3390's..
I know that the MVS 3.8J distributed on Volker Bandke's Turnkey3
system has support for 3380's, but I doubt there is 3390 support there.

Post by a***@public.gmane.org
Cheers,
Abe.

I suppose the only way you are going to find out is to "suck it and see".

[a***@public.gmane.org]

John,

Age!! Shit, I've used 8" floppies.
**--> Welcome to the club!

Post by a***@public.gmane.org
Returning to the 3390 volumes - as they are
verbatim copies of the original OS2-supported
virtual 3390 volumes, I thought/hoped that
I might be able to install Hercules, and
then mount these files to as virtual 3390s
to the Hercules system.

Why not just try it? To me the costs to you seem to be time and
bandwidth.
**--> time is the major constraint. I once tried installing
Hercules, and failed to get it working. I thought I'd ask
to verify if another effort might be worth the investment
in time.

If Herc does support the disk format the 3390 images you have, then
the OS you are running under Herc also needs to support 3390's..
I know that the MVS 3.8J distributed on Volker Bandke's Turnkey3
system has support for 3380's, but I doubt there is 3390 support there.
**--> Thanks for the hint! I still have some ADCD distro's.
So I'd have to get those up and running before trying
to attach the old 3390 files.

I suppose the only way you are going to find out is to "suck it and see".
**--> Yes, somewhen in the next couple of years ;-)
I'll settle for the next three months.
With the info I've got it seems worthwhile to
try this to retrieve the old source files.

Thanks for your help,
Abe.
===

[Jay Maynard]

Post by a***@public.gmane.org
Returning to the 3390 volumes - as they are
verbatim copies of the original OS2-supported
virtual 3390 volumes, I thought/hoped that
I might be able to install Hercules, and
then mount these files to as virtual 3390s
to the Hercules system.

Yes. These files are in AWSCKD format, which is the native format Hercules
uses for uncompressed CKD DASD images. You can use them as is, or use the
dasdcopy utility to copy them to compressed CKD files which will also work
with Hercules and save a significant amount of space.

You can also use the dmap2hrc utility to help convert your P/390 devmap file
to a Hercules configuration file. You'll have to do some manual editing of
the file after you've run the utility, but it'll be a good start.

Both the dasdcopy and dmap2hrc utilities are standard parts of Hercules.

Post by a***@public.gmane.org
Come to think of it, those old 3390s were
not complete 3390-9 volumes; they had fewer
cylinders to make the virtual volume fit
within a single physical file. Larger volumes
were supported using two files.

Make sure both files are available to Hercules. When defining the volume in
the Hercules configuration file, just define the first file (the one with -1
in the filename); Hercules will figure out the second file is needed and
find it automatically.

[Lindy Mayfield]

Can someone help me figure out what I'm doing wrong here?



I'm following the instructions on this page for installing zLinux:

http://www.josefsipek.net/docs/s390-linux/



I have Hercules running on Windows and part of my config looks like
this:



# reader

000C 3505 c:\zlinux\rdr\kernel.debian
c:\zlinux\rdr\parmfile.debian c:\zlinux\rdr\initrd.debian autopad eof

# dasd

0120 3390 c:\zlinux\dasd\3390.LINUX.0120

0121 3390 c:\zlinux\dasd\3390.LINUX.0121



When I IPL 00C I get this error:



ipl c

HHCCP048I 000C:CCW=27000000 60000001=>00080000 80000240 27000000
60000001 ......

HHCCP075I 000C:Stat=0E00 Count=0001

HHCCP076I 000C:Sense=80000000 00000000 00000000 00000000 00000000
00000000

HHCCP077I 000C:Sense=CMDREJ

HHCCP029E z/Arch mode IPL failed: CSW status=0E00

Sense=80000000



So I thought maybe there is something wrong with 00C. Devlist shows:

devlist

0:0009 3215

0:000C 3505 c:\zlinux\rdr\kernel.debian ebcdic autopad eof open

0:000E 1403 c:\zlinux\prt\print00e.txt crlf

0:001F 3270

0:0120 3390 c:/zlinux/dasd/3390.LINUX.0120 [3339 cyls] open

0:0121 3390 c:/zlinux/dasd/3390.LINUX.0121 [3339 cyls] open

0:0581 3420 *

0:0A00 3088 CTCI 192.168.50.3/0.0.0.0 (tun0) open

0:0A01 3088 CTCI 192.168.50.3/0.0.0.0 (tun0) open



Does is mean something that 00C only shows ./kernel.debian and not all
three files, or is that a red herring? Or maybe it is something else I
did funny?



I tried relative paths like ./rdr/kernel.debian etc. and with the /'s
going both ways but that wasn't it. Same errors. (See below.)



Thanks in advance for any hints, help, advice.



Regards,

Lindy



<< Full Config File >>



CPUSERIAL 000069 # CPU serial number

CPUMODEL 9672 # CPU model number

MAINSIZE 256 # Main storage size in megabytes

XPNDSIZE 0 # Expanded storage size in megabytes

CNSLPORT 3270 # TCP port number to which consoles connect

NUMCPU 2 # Number of CPUs

LOADPARM 0120.... # IPL parameter

OSTAILOR LINUX # OS tailoring

PANRATE SLOW # Panel refresh rate (SLOW, FAST)

ARCHMODE ESAME # Architecture mode ESA/390 or ESAME

# .-----------------------Device number

# | .-----------------Device type

# | | .---------File name and parameters

# | | |

# V V V

#--- ---- --------------------

# console

001F 3270

# terminal

0009 3215

# reader

000C 3505 ./rdr/kernel.debian ./rdr/parmfile.debian
./rdr/initrd.debian autopad eof

# printer

000E 1403 ./prt/print00e.txt crlf

# dasd

0120 3390 ./dasd/3390.linux.0120

0121 3390 ./dasd/3390.linux.0121

# tape

0581 3420

# network s390 realbox

0A00,0A01 CTCI -n 02-00-4C-4F-4F-50 192.168.50.3 0.0.0.0





[Non-text portions of this message have been removed]

[Rob van der Heij]

Post by Lindy Mayfield
Thanks in advance for any hints, help, advice.

It might be that this particular kernel is built without the option
that gets the loader in front of the kernel.

Much easier approach is to prepare a ".ins" file and IPL that file
(this causes the 3 files to be loaded into S/390 memory and runs it).
Create a "linux.ins" file like this listing the individual files and
their location in memory (kernel and initrd are fixed locations,
parmfile overlays part of the kernel).

boot/vmrdr.ikr 0x00000000
boot/initrd 0x00800000
boot/parmfile 0x00010480

You the use "IPL linux.ins" in Hercules to get going.

Rob

[Lindy Mayfield]

Thanks, Rob, that did it.



________________________________

From: hercules-390-***@public.gmane.org [mailto:hercules-390-***@public.gmane.org]
On Behalf Of Rob van der Heij
Sent: 2. tammikuuta 2008 14:37
To: hercules-390-***@public.gmane.org
Subject: Re: [hercules-390] Problem IPL'ing Debian zLinux

Post by Lindy Mayfield
Thanks in advance for any hints, help, advice.

It might be that this particular kernel is built without the option
that gets the loader in front of the kernel.

Much easier approach is to prepare a ".ins" file and IPL that file
(this causes the 3 files to be loaded into S/390 memory and runs it).
Create a "linux.ins" file like this listing the individual files and
their location in memory (kernel and initrd are fixed locations,
parmfile overlays part of the kernel).

boot/vmrdr.ikr 0x00000000
boot/initrd 0x00800000
boot/parmfile 0x00010480

You the use "IPL linux.ins" in Hercules to get going.

Rob





[Non-text portions of this message have been removed]

[Ivan Warren]

Post by Rob van der Heij

Post by Lindy Mayfield
Thanks in advance for any hints, help, advice.

It might be that this particular kernel is built without the option
that gets the loader in front of the kernel.
Much easier approach is to prepare a ".ins" file and IPL that file
(this causes the 3 files to be loaded into S/390 memory and runs it).
Create a "linux.ins" file like this listing the individual files and
their location in memory (kernel and initrd are fixed locations,
parmfile overlays part of the kernel).
boot/vmrdr.ikr 0x00000000
boot/initrd 0x00800000
boot/parmfile 0x00010480
You the use "IPL linux.ins" in Hercules to get going.
Rob

Even better than my tape trick ;)

--Ivan

[Lindy Mayfield]

Oh bother. Is this going to be difficult? (-:

Now I get this:



Configure the network device

----------------------------



Please choose the type of your primary network interface that you will
need for

installing the Debian system (via NFS or HTTP). Only the listed devices
are

supported.

Network device type:

1. ctc: Channel to Channel (CTC) or ESCON connection *!

2. qeth: OSA-Express in QDIO mode / HiperSockets

3. iucv: Inter-User Communication Vehicle - available for VM guests
only

Prompt: '?' for help, default=1>

.1

1



ERROR: No CTC or ESCON connections



Please make sure that you have set them up correctly.

Press enter to continue!



But devlist shows that I have CTCI adapters defined.

devlist

0:0009 3215

0:000C 3505 ./rdr/kernel.debian autopad eof

0:000E 1403 ./prt/print00e.txt crlf

0:001F 3270

0:0120 3390 ./dasd/3390.linux.0120 [3339 cyls] ope

0:0121 3390 ./dasd/3390.linux.0121 [3339 cyls] ope

0:0581 3420 *

0:0A00 3088 CTCI 192.168.50.3/0.0.0.0 (tun0) open

0:0A01 3088 CTCI 192.168.50.3/0.0.0.0 (tun0) open



Defined like this:

# network s390 realbox

0A00,0A01 3088 CTCI -n 02-00-4C-4F-4F-50 192.168.50.3 0.0.0.0



Lindy





________________________________

From: hercules-390-***@public.gmane.org [mailto:hercules-390-***@public.gmane.org]
On Behalf Of Ivan Warren
Sent: 2. tammikuuta 2008 14:49
To: hercules-390-***@public.gmane.org
Subject: Re: [hercules-390] Problem IPL'ing Debian zLinux

Post by Rob van der Heij

Post by Lindy Mayfield
Thanks in advance for any hints, help, advice.

It might be that this particular kernel is built without the option
that gets the loader in front of the kernel.
Much easier approach is to prepare a ".ins" file and IPL that file
(this causes the 3 files to be loaded into S/390 memory and runs it).
Create a "linux.ins" file like this listing the individual files and
their location in memory (kernel and initrd are fixed locations,
parmfile overlays part of the kernel).
boot/vmrdr.ikr 0x00000000
boot/initrd 0x00800000
boot/parmfile 0x00010480
You the use "IPL linux.ins" in Hercules to get going.
Rob

Even better than my tape trick ;)

--Ivan





[Non-text portions of this message have been removed]

[Martin T2..]

Lindy,

Is this going to be difficult? <<

Certainly not- I did it as well (as absolute novice to LINUX).

CTC- my defintion is exactly like yours- but I have a "-" where you have
a comma.

0440-0441 CTCI -n 02-00-4c-4f-4f-50 192.168.47.2 0.0.0.0

but the DEVLIST against it show the same as yours.

Did you use the CTCI-defintion in VSE or MVS before (so you know that it
does work)?

[Rob van der Heij]

Post by Lindy Mayfield
ERROR: No CTC or ESCON connections

Did you see any other errors during startup of Hercules w.r.t. the CTC's ?

If you have a fairly recent Linux distribution as the hypervisor, you
may need to tame udev to ensure the permission bits on /dev/net/tun
are set right. A "permission denied" is not good news during startup
(a message about ioctl is no problem).

If you're trying this on windows, I have nothing to offer but my
condolences ... ;-)

Rob

[Lindy Mayfield]

I will accept your condolences... for now. (-: I can move it over to
my Linux machine easily if I have to, but I wanted it running on my work
laptop if I could.



Startup looked ok:



Machine dependent assists: cmpxchg1 cmpxchg4 cmpxchg8 fetch_dw
store_dw +

Running on SASPC311 Windows_NT-5.1 i686 MP=2

Crypto module loaded (c) Copyright Bernard van der Helm, 2003-2007

HHCCF065I Hercules: tid=00000298, pid=3792, pgid=3792, priority=0

HHCTE001I Console connection thread started: tid=00000AAC, pid=3792

HHCTE003I Waiting for console connection on port 3270

HHCDA020I ./dasd/3390.linux.0120 cyls=3339 heads=15 tracks=50085
trklen=56832

HHCDA020I ./dasd/3390.linux.0121 cyls=3339 heads=15 tracks=50085
trklen=56832

TunTap32.dll version 3.2.1.160 initiated

HHCCT073I 0A00: TUN device tun0 opened

HHCCF069I Run-options enabled for this run:

NUMCPU: 2

ASN-and-LX-reuse: DISabled

DIAG8CMD: DISabled

HHCCP002I CPU0000 thread started: tid=0000043C, pid=3792, priority=15

HHCTT002I Timer thread started: tid=00000C60, pid=3792, priority=0

HHCCP003I CPU0000 architecture mode z/Arch

HHCCP002I CPU0001 thread started: tid=000001F8, pid=3792, priority=15

HHCCP003I CPU0001 architecture mode z/Arch

HHCPN001I Control panel thread started: tid=00000298, pid=3792

HHCAO001I Hercules Automatic Operator thread started;

tid=00000660, pri=0, pid=3792



And also the tun/tap stuff runs fine on another OS on Hercules on
Windows so I know Windows is configured OK.



Well, I won't get to crazy trying to figure it out before trying Linux.
Maybe it is because I'm using the latest version of Debian, 4.1 I think
it was. I could go back one to 4.0 which we know works.



I appreciate everyone's help. Oh, and I tried the 0A00-0A01 syntax
instead of the comma, just in case. Same thing.



So, do I download the 4.0 stuff or try Linux... I think easier to d/l
4.0 first. I'll post what happens if it works. Or not.



Lindy



________________________________

From: hercules-390-***@public.gmane.org [mailto:hercules-390-***@public.gmane.org]
On Behalf Of Rob van der Heij
Sent: 2. tammikuuta 2008 15:50
To: hercules-390-***@public.gmane.org
Subject: Re: [hercules-390] Problem Installing Debian zLinux

Post by Lindy Mayfield
ERROR: No CTC or ESCON connections

Did you see any other errors during startup of Hercules w.r.t. the CTC's
?

If you have a fairly recent Linux distribution as the hypervisor, you
may need to tame udev to ensure the permission bits on /dev/net/tun
are set right. A "permission denied" is not good news during startup
(a message about ioctl is no problem).

If you're trying this on windows, I have nothing to offer but my
condolences ... ;-)

Rob





[Non-text portions of this message have been removed]

[Lindy Mayfield]

Ah, it must be a problem with the latest. Not sure but I think I have
4.0r0 now from here:

http://http.us.debian.org/debian/dists/oldstable/main/installer-s390/cur
rent/images/tape/



Anyway, I'm moving further now.



________________________________

From: hercules-390-***@public.gmane.org [mailto:hercules-390-***@public.gmane.org]
On Behalf Of Lindy Mayfield
Sent: 2. tammikuuta 2008 16:40
To: hercules-390-***@public.gmane.org
Subject: RE: [hercules-390] Problem Installing Debian zLinux


So, do I download the 4.0 stuff or try Linux... I think easier to d/l
4.0 first. I'll post what happens if it works. Or not.

Lindy





[Non-text portions of this message have been removed]

[Frans Pop]

Post by Lindy Mayfield
Ah, it must be a problem with the latest. Not sure but I think I have
http://http.us.debian.org/debian/dists/oldstable/main/installer-s390/cu
r rent/images/tape/

No, oldstable = sarge = 3.1.

For Etch (4.0), replace oldstable by stable.

Cheers,
FJP

[Lindy Mayfield]

I wanted to try 4.0r0. Where would I find that one?



BTW, I tried the latest stable, 4.0r1 on Linux with the same errors
about not recognizing the CTCI device. Oldstable ( 3.1) seems to work
ok, at least up to that part.



I gave up on Windows because I couldn't get the networking to work from
zLinux through my loopback-adapter to the outside. Not even sure it can
work with all the VPN stuff I have running.



________________________________

From: hercules-390-***@public.gmane.org [mailto:hercules-390-***@public.gmane.org]
On Behalf Of Frans Pop
Sent: 2. tammikuuta 2008 19:36
To: hercules-390-***@public.gmane.org
Subject: Re: [hercules-390] Problem Installing Debian zLinux

Ah, it must be a problem with the latest. Not sure but I think I have

http://http.us.debian.org/debian/dists/oldstable/main/installer-s390/cu
<http://http.us.debian.org/debian/dists/oldstable/main/installer-s390/cu

r rent/images/tape/

No, oldstable = sarge = 3.1.

For Etch (4.0), replace oldstable by stable.

Cheers,
FJP



[Non-text portions of this message have been removed]

[Frans Pop]

Post by Lindy Mayfield
I wanted to try 4.0r0. Where would I find that one?

It's no longer available. Only the "current" release is.

Post by Lindy Mayfield
BTW, I tried the latest stable, 4.0r1 on Linux with the same errors
about not recognizing the CTCI device. Oldstable ( 3.1) seems to work
ok, at least up to that part.

AFAIK it should work fine. I'll do a test myself tomorrow when I get home
and let you know the result.

Cheers,
FJP

[Frans Pop]

Post by Frans Pop

Post by Lindy Mayfield
BTW, I tried the latest stable, 4.0r1 on Linux with the same errors
about not recognizing the CTCI device. Oldstable ( 3.1) seems to work
ok, at least up to that part.

AFAIK it should work fine. I'll do a test myself tomorrow when I get home
and let you know the result.

Sorry, slightly delayed due to flue.

I've just tested the current Etch generic installer image on my own Hercules
setup (host system is Debian Linux), and had no problem at all with network
configuration.

I have the following in my hercules.cnf:
0A00 3088 CTCI /dev/net/tun 1500 10.19.92.1 10.19.92.2 255.255.255.0
0A01 3088 CTCI /dev/net/tun 1500 10.19.92.1 10.19.92.2 255.255.255.0

Which gives in the hercules console:
J 0A00 3088 CTCA CTCI 10.19.92.1/10.19.92.2 (tun0)
K 0A01 3088 CTCA CTCI 10.19.92.1/10.19.92.2 (tun0)

During installation I select the following options (".." is equivalent to
<enter> and accepts the default).

Configure the network device
----------------------------

Please choose the type of your primary network interface that you will need
for installing the Debian system (via NFS or HTTP). Only the listed devices
are supported.
Network device type:
1. ctc: Channel to Channel (CTC) or ESCON connection
2. qeth: OSA-Express in QDIO mode / HiperSockets
3. iucv: Inter-User Communication Vehicle - available for VM guests only
Prompt: '?' for help>
Command ==> .1

The following device numbers might belong to CTC or ESCON connections.
CTC read device:
1. 0.0.0a00 2. 0.0.0a01
Prompt: '?' for help>
Command ==> .1

The following device numbers might belong to CTC or ESCON connections.
CTC write device:
1. 0.0.0a00 2. 0.0.0a01
Prompt: '?' for help>
Command ==> .2

Protocol for this connection:
1. S/390 (0) *! 2. Linux (1) 3. OS/390 (3)
Command ==> ..

The configured parameters are:
read channel = 0.0.0a00
write channel = 0.0.0a01
protocol = S/390

Do you accept this configuration?
1. Yes *! 2. No
Prompt: '?' for help, default=1>
Command ==> ..

Configure a network using static addressing
-------------------------------------------

The IP address is unique to your computer and consists of four numbers
separated by periods. If you don't know what to use here, consult your
network administrator.
IP address:
Prompt: '?' for help>
Command ==> .10.19.92.1

The point-to-point address is used to determine the other endpoint of the
point to point network. Consult your network administrator if you do not
know the value. The point-to-point address should be entered as four
numbers separated
by periods.
Point-to-point address:
Prompt: '?' for help>
Command ==> .10.19.92.2

The name servers are used to look up host names on the network. Please enter
the IP addresses (not host names) of up to 3 name servers, separated by
spaces. Do not use commas. The first name server in the list will be the
first to be queried. If you don't want to use any name server, just leave
this field blank.
Name server addresses:
Prompt: '?' for help, default=10.19.92.2>
Command ==> .10.19.66.2

Currently configured network parameters:

interface = ctc0
ipaddress = 10.19.92.1
netmask = 255.255.255.255
gateway = 10.19.92.2
pointopoint = 10.19.92.2
nameservers = 10.19.66.2

Is this information correct?
1. Yes *! 2. No
Prompt: '?' for help, default=1>
Command ==> ..

[Ivan Warren]

Post by Lindy Mayfield
ipl c
HHCCP048I 000C:CCW=27000000 60000001=>00080000 80000240 27000000
60000001 ......
HHCCP075I 000C:Stat=0E00 Count=0001
HHCCP076I 000C:Sense=80000000 00000000 00000000 00000000 00000000
00000000
HHCCP077I 000C:Sense=CMDREJ

It seems you may be using a "tape" version of the kernel.. (X'27' would
be a BSB order - and doesn't work on a card reader)..

So you are either using the wrong kernel or linux and/or debian made a
mistake with the kernel build (either the linux folks added provision
for tape only CCWs - even if the kernel is to be built for a RDR IPL, or
debian did, or the build has a mistake in it).

Alternatively, you may try this :

Instead of doing a reader IPL, you can do a tape IPL by doing as follows :

Create a file ending with a TDF extension (example debian.tdf). In it,
put the following :
@TDF
<path to your kernel> FIXED RECSIZE 80
<path to your parmfile> TEXT
<path to your initrd> FIXED RECSIZE 80

Add a tape definition to your configuration file. For example

181 3480 <path to your TDF file>

And instead of IPL 00C, issue IPL 181

Once the kernel is up with the installer initrd, then the rest should be
business as usual..

HTH,

--Ivan

[a***@public.gmane.org]

Jay,

Yes. These files are in AWSCKD format, which is the native format Hercules
uses for uncompressed CKD DASD images. You can use them as is, or use the
dasdcopy utility to copy them to compressed CKD files which will also work
with Hercules and save a significant amount of space.
**--> Ok - I'll prefer the vanilla version, I think.

You can also use the dmap2hrc utility to help convert your P/390 devmap file
to a Hercules configuration file. You'll have to do some manual editing of
the file after you've run the utility, but it'll be a good start.
Both the dasdcopy and dmap2hrc utilities are standard parts of Hercules.
**--> Ok - it's good to know that.

Post by a***@public.gmane.org
Come to think of it, those old 3390s were
not complete 3390-9 volumes; they had fewer
cylinders to make the virtual volume fit
within a single physical file. Larger volumes
were supported using two files.

Make sure both files are available to Hercules. When defining the volume in
the Hercules configuration file, just define the first file (the one with -1
in the filename); Hercules will figure out the second file is needed and
find it automatically.
**--> Ok, that'll help me set up the ADCD version of OS/390
that I'll need to read the 3390's. IIRC, they contained various
full-sized 3390 volumes.

Thanks a lot! You've given me the info I needed
to convince myself it's worth the effort to set up
Hercules and try to retrieve my old source code.

Abe.
===

[halfmeg]

Post by a***@public.gmane.org
I still have some backup copies of my old virtual 3390 volumes.
These files originated from my P390, which is not currently
available to me.
I just wondered whether I might use Hercules to access these
volumes to extract some source files that are on those old 3390s.
Any chance hercules can do that - or does it use an entirely
different internal structure for its virtual 3390 devices?

The quickest method to 'see' is try running the DASDLS utility against
one of them. It should list the VTOC. Then you might be able to use
DASDPDSU to unload your files without having to IPL an OS under
Hercules and attach them to a configured device, etc, etc..

Phil - DASDPDSU may still be stuck with only working with LRECL 80 and
just checking CVS source it still truncates output to 72 columns when
translate to ASCII is requested

[a***@public.gmane.org]

Ok, thanks for the info.

I'm planning to get hercules up and running.
In case I fail again, I'll try the method you
mentioned, even though I'd prefer to retain
the sequence numbers.

Cheers,
Abe.
===



----- Original Message -----
From: halfmeg
To: hercules-390-***@public.gmane.org
Sent: Saturday, January 05, 2008 5:31 AM
Subject: [hercules-390] Re: Old virtual 3390 volumes

Post by a***@public.gmane.org
I still have some backup copies of my old virtual 3390 volumes.
These files originated from my P390, which is not currently
available to me.
I just wondered whether I might use Hercules to access these
volumes to extract some source files that are on those old 3390s.
Any chance hercules can do that - or does it use an entirely
different internal structure for its virtual 3390 devices?

The quickest method to 'see' is try running the DASDLS utility against
one of them. It should list the VTOC. Then you might be able to use
DASDPDSU to unload your files without having to IPL an OS under
Hercules and attach them to a configured device, etc, etc..

Phil - DASDPDSU may still be stuck with only working with LRECL 80 and
just checking CVS source it still truncates output to 72 columns when
translate to ASCII is requested





[Non-text portions of this message have been removed]