--- In hercules-390@yahoogroups.com, "somitcw" <somitcw@...> wrote:
>
> --- In hercules-390@yahoogroups.com,
> "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 ?