Filemode numbers normally don't play games with you, except: when storing files on 190 or 19E, the number should be 2, else the files are invisible after an IPL CMS And filemode 0 is -by default- invisible on R/O linked minidisks, but I saw you used an SFS dir.
How did you upload the modules? It should be binary and most probably LRECL 1024, RECFM F and then you would need to execute COPYFILE (UNPACK on the uploaded files. It is namely impossible to transmit a binary fle as RECFM V files through the PC world where files have no recordlengths, therefore one must make these files RECFM F somehow, VMARC creates F80; COPYFILE PACK creates F1024. 2007/8/8, Adam Thornton <[EMAIL PROTECTED]>: > > On Aug 8, 2007, at 1:34 PM, Mark Pace wrote: > > > I can't find it now. But it was on EAGACTAL exec. I'm pretty > > certain it had something to do with the FileMode. I think it was > > copying it as H0 or H1 and needed to be H2, or something like that. > > I changed it to be H2. > > No dice: > > listf * module h > EAGRTPRC MODULE H2 > EAGRTLIB MODULE H2 > Ready; T=0.01/0.01 14:50:09 > eagrtprc > DMSMOD639E Error loading module EAGRTPRC, return code 11 from LOADMOD > > > *I* think the problem is that the modules got corrupted during > upload; FTP from systems which don't understand structured record > formats tends to do that to me. A VMARC would make this just go > away, I again hint strongly while clearing my throat in IBM's direction. > > Adam > -- Kris Buelens, IBM Belgium, VM customer support
