Many weeks ago I asked about others having a problem with mksysb
failing on AIX
4.1 systems if you also used ADSM and dsm space management.

Several folks emailed me that they had the same problem so I thought I
would post
the final resolution here.

Problem is fixed for Aix 4.1 users with apar:  IX67764.
this is a retro fit of a fix that was created for 4.2 users for mksysb
problems.

The symptoms of the failure (that I had) were


> bosboot: Boot image is 5932 512 byte blocks.
> mount: 0506-324 Cannot mount /vet1 on /ethan/vet1: A system call
> received a para
> meter that is not valid.
> mount: 0506-324 Cannot mount /vet2 on /ethan/vet2: A system call
> received a para
> meter that is not valid.
> umount: 0506-347 Cannot find anything to unmount.
> umount: 0506-347 Cannot find anything to unmount.

(note: vet1 and
> vet2 are my jfs systems that are managed by hsm.  they are not on the
> rootvg, but in
> separate user volume groups) :

the mksysb continues and "says" it completed successfully but there is
some concern
as to whether the tape is good or not.

My fix got rid of all the error messages and any references to my space
managed filesystems and the mksysb proceeds normally.

Susie McClure
Rice University