loading data

[phn2icarus]

I've used the dasdload utility to move a bunch of xmit datasets to a new dasd. the problem is that once i ipl my system with the new dasd i get the message vtoc error, once i try to check the dasd content by 3.4 option. Could someone give a hint about this ?

[Gerhard Postpischil]

phn2icarus wrote:
> I've used the dasdload utility to move a bunch of xmit
> datasets to a new dasd. the problem is that once i ipl my
> system with the new dasd i get the message vtoc error, once i
> try to check the dasd content by 3.4 option. Could someone
> give a hint about this ?

Is it possible that you have a device type mismatch between the
type of PC file you created, and the one MVS assumes at the
address you specified in the config file?  On MVS, you can issue
a D U (display units), and that should let you figure out what
you have and what you need. If that's not it, you'd need to
supply a lot more information on what you did, and what messages
  you're getting. Also make sure you have the latest version of
the Hercules utilities; some of the ones distributed with the
turnkey CD (and image) had errors. (I've used the tk3 version of
the utilities for dasdload w/xmit file, and had no problems)




Gerhard Postpischil
Bradford, VT

[somitcw-2]

--- In hercules-390@...,
 "phn2icarus" <phn2icarus@...> wrote:
> I've used the dasdload utility to move a bunch of
>xmit datasets to a new dasd. the problem is that
>once i ipl my system with the new dasd i get the
>message vtoc error, once i try to check the dasd
>content by 3.4 option. Could someone give a hint
>about this ?

   The ISPF/PDF option 3.4 makes me assume zOS.

   You did not post the error message.
copy/paste is your friend.  In 3.4, with the
short error message on the screen, did you
press PF1 to get a long error message?

   My guess would be that either the device is
to large to have a format 5 DSCB ( 3390-9 and up )
or dasdload does not manage a format 5 DSCB so
free space information is incorrect on the disk.
To fix, allocate a data on the disk to tell zOS
to build proper free space information.

//JOB JOB JOB,JOB JOB
//IEFBR14 EXEC PGM=IEFBR14
//TEMP DD UNIT=3390,VOL=SER=xxxxxx,SPACE=(TRK,1)
//* ISPF/PDF option =3.2 would also work.

   You will get a console message saying that
either the DIRF or DOS comtamination bit was on
so format 5 or 7 free space information is being
rebuild.

[somitcw-2]

--- In hercules-390@...,
"phn2icarus" <phn2icarus@...> wrote:
> I've used the dasdload utility to move a bunch of
>xmit datasets to a new dasd. the problem is that
>once i ipl my system with the new dasd i get the
>message vtoc error, once i try to check the dasd
>content by 3.4 option. Could someone give a hint
>about this ?

The ISPF/PDF option 3.4 makes me assume zOS.

You did not post the error message.
copy/paste is your friend. In 3.4, with the
short error message on the screen, did you
press PF1 to get a long error message?

My guess would be that either the device is too
large to use a format 5 DSCB ( 3390-9 and up )
or dasdload does not manage a format 5 DSCB so
free space information is incorrect on the disk.
To fix, allocate a data on the disk to tell zOS
to build proper free space information.

//JOB JOB JOB,JOB JOB
//IEFBR14 EXEC PGM=IEFBR14
//TEMP DD UNIT=3390,VOL=SER=xxxxxx,SPACE=(TRK,1)
//* ISPF/PDF option =3.2 would also work.

You will get a console message saying that
either the DIRF or DOS comtamination bit was on
so format 5 or 7 free space information is being
rebuilt.

[somitcw-2]

--- In hercules-390@...,
"phn2icarus" <phn2icarus@...> wrote:
> I've used the dasdload utility to move a bunch of
>xmit datasets to a new dasd. the problem is that
>once i ipl my system with the new dasd i get the
>message vtoc error, once i try to check the dasd
>content by 3.4 option. Could someone give a hint
>about this ?

The ISPF/PDF option 3.4 makes me assume zOS.

You did not post the error message.
copy/paste is your friend. In 3.4, with the
short error message on the screen, did you
press PF1 to get a long error message?

My guess would be that either the device is too
large to use a format 5 DSCB ( 3390-9 and up )
or dasdload does not manage a format 5 DSCB so
free space information is incorrect on the disk.
To fix, allocate a data set on the disk to tell
zOS to build proper free space information.

//JOB JOB JOB,JOB JOB
//IEFBR14 EXEC PGM=IEFBR14
//TEMP DD UNIT=3390,VOL=SER=xxxxxx,SPACE=(TRK,1)
//* ISPF/PDF option =3.2 A and D would also work.

You will get a console message saying that
either the DIRF or DOS contamination bit was on
so format 5 or 7 free space information is being
rebuilt.

[Fausto Saporito-2]

Hello all,

is there any plans to include the emulation of OSA cards in QDIO mode or HyperSocket?

Thanks,
Fausto


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

[phn2icarus]

--- In hercules-390@..., "somitcw" <somitcw@...> wrote:

>
> --- In hercules-390@...,
> "phn2icarus" <phn2icarus@> wrote:
> > I've used the dasdload utility to move a bunch of
> >xmit datasets to a new dasd. the problem is that
> >once i ipl my system with the new dasd i get the
> >message vtoc error, once i try to check the dasd
> >content by 3.4 option. Could someone give a hint
> >about this ?
>
> The ISPF/PDF option 3.4 makes me assume zOS.
>
> You did not post the error message.
> copy/paste is your friend. In 3.4, with the
> short error message on the screen, did you
> press PF1 to get a long error message?
>
> My guess would be that either the device is too
> large to use a format 5 DSCB ( 3390-9 and up )
> or dasdload does not manage a format 5 DSCB so
> free space information is incorrect on the disk.
> To fix, allocate a data set on the disk to tell
> zOS to build proper free space information.
>
> //JOB JOB JOB,JOB JOB
> //IEFBR14 EXEC PGM=IEFBR14
> //TEMP DD UNIT=3390,VOL=SER=xxxxxx,SPACE=(TRK,1)
> //* ISPF/PDF option =3.2 A and D would also work.
>
> You will get a console message saying that
> either the DIRF or DOS contamination bit was on
> so format 5 or 7 free space information is being
> rebuilt.
>

I tried running the job, but it didn't work. Any other idea ?
does anyone would like to post a step by step of a dasd build process with xmit files included ?

[phn2icarus]

--- In hercules-390@..., "somitcw" <somitcw@...> wrote:

>
> --- In hercules-390@...,
> "phn2icarus" <phn2icarus@> wrote:
> > I've used the dasdload utility to move a bunch of
> >xmit datasets to a new dasd. the problem is that
> >once i ipl my system with the new dasd i get the
> >message vtoc error, once i try to check the dasd
> >content by 3.4 option. Could someone give a hint
> >about this ?
>
> The ISPF/PDF option 3.4 makes me assume zOS.
>
> You did not post the error message.
> copy/paste is your friend. In 3.4, with the
> short error message on the screen, did you
> press PF1 to get a long error message?
>
> My guess would be that either the device is too
> large to use a format 5 DSCB ( 3390-9 and up )
> or dasdload does not manage a format 5 DSCB so
> free space information is incorrect on the disk.
> To fix, allocate a data set on the disk to tell
> zOS to build proper free space information.
>
> //JOB JOB JOB,JOB JOB
> //IEFBR14 EXEC PGM=IEFBR14
> //TEMP DD UNIT=3390,VOL=SER=xxxxxx,SPACE=(TRK,1)
> //* ISPF/PDF option =3.2 A and D would also work.
>
> You will get a console message saying that
> either the DIRF or DOS contamination bit was on
> so format 5 or 7 free space information is being
> rebuilt.
>

I tried running the job, but it didn't work. Any other idea ?
does anyone would like to post a step by step of a dasd build process with xmit files included ?

[somitcw-2]

--- In hercules-390@...,
 "phn2icarus" <phn2icarus@...> wrote:
> I tried running the job, but it didn't work.
>Any other idea ? does anyone would like to post
>a step by step of a dasd build process with xmit
>files included ?

For dasdload examples, do a yahoo search for: dasdload

You haven't posted what operating system you are using.

You haven't posted your dasdload messages.

You haven't posted your VTOC error messages.

You haven't posted the JOB "didn't work" messages.

For the JOB, did you get a JCL error?  Which one?
Did your system not like the JOB statement:
//JOB JOB JOB,JOB
or refuse to mount VOL=SER=xxxxxx after conplaining
about lower-case letters not enclosed in tick marks?

Unless you can copy/paste some additional information,
"didn't work" does not provide enough for me to assist.
Perhaps someone else can guess?

[kerravon86]

--- In hercules-390@..., "phn2icarus" <phn2icarus@...> wrote:

>
> > //JOB JOB JOB,JOB JOB
> > //IEFBR14 EXEC PGM=IEFBR14
> > //TEMP DD UNIT=3390,VOL=SER=xxxxxx,SPACE=(TRK,1)
> > //* ISPF/PDF option =3.2 A and D would also work.
> >
> > You will get a console message saying that
> > either the DIRF or DOS contamination bit was on
> > so format 5 or 7 free space information is being
> > rebuilt.
>
> I tried running the job, but it didn't work. Any other idea ?

You are meant to modify the jobcard and volser
yourself, and it looks to me like you would
need a disp=(,pass) statement on the DD too.

> does anyone would like to post a step by step of
> a dasd build process with xmit files included ?

Well, I sort of followed this myself yesterday:

http://www.bsp-gmbh.com/turnkey/cookbook/hercules/hercload.html

until I remembered that I once saw a whole lot of
weird .ctl files in c:\mvs380\conf and found an
mvscat.ctl that had what I needed to create a
3390 with a sensible size VTOC.

I briefly considered another modification to
dasdload but then decided I didn't have anything
particularly sensible myself. Maybe a cylinder
would be sensible, but I have better things to
do in life than modify dasdload. Well, maybe
that's an exaggeration.

BFN.  Paul.

[somitcw-2]

--- In hercules-390@...,
 "kerravon86" <kerravon86@...> wrote:

> --- In hercules-390@...,
>"phn2icarus" <phn2icarus@> wrote:
>>> //JOB JOB JOB,JOB JOB
>>> //IEFBR14 EXEC PGM=IEFBR14
>>> //TEMP DD UNIT=3390,VOL=SER=xxxxxx,SPACE=(TRK,1)
>>> //* ISPF/PDF option =3.2 A and D would also work.
>>> You will get a console message saying that
>>>either the DIRF or DOS contamination bit was on
>>>so format 5 or 7 free space information is being
>>>rebuilt.
>> I tried running the job, but it didn't work.
>>Any other idea ?
> You are meant to modify the jobcard and volser
>yourself, and it looks to me like you would
>need a disp=(,pass) statement on the DD too.

- - - snipped - - -

   The JOB statement is valid for many OS/360,
MVS, OS/390, and zOS systems.  Local modifications
may require a different JOB name, account codes,
programmer name, a JOB CLASS parameter, a MSGCLASS
parameter, a TIME parameter, etcetera.
( Paul doesn't like the etc. abbreviation. )

   xxxxxx in the VOL=SER=xxxxxx parameter should
be changed to the volser having the VTOC errors
that were not posted.

   Default DISP is DISP=(NEW,DELETE,DELETE) which
is wanted so defaulted to.

   ISPF/PDF option =3.2 A then D would also work.