Rather than fight file transfers prior to installing licenses, use the following command:
$ @SYS$UPDATE:VMSLICENSE The command procedure will guide one through the license data entry in the order and format as on the hardcopy license. The format for a command file is as below. The various options will differ based on the type of license. $ LICENSE REGISTER xxxxxxxxxx - /ISSUER=yyyyyyy - /AUTHORIZATION=zzzzzzzzzzzzzz - /PRODUCER=aaaaaaaa - /UNITS=bbbbbbbb - /OPTIONS=(cccccccccc) - /CHECKSUM=ddddddddddddddd $ LICENSE LOAD xxxxxxxxxxx/LOG/PRODUCER=aaaaaaaaaa $! $ exit $! $! [End of File] VMS attempts to "strong type" files, i.e. it has many supported formats and one must ensure that the file being used corresponds to a viable format. It is not unusual for a file to have <cr><lf> but not the proper attributes. The method for correcting such is VMS version specific, in that the earlier versions used different command/utilities to modify the file header for the various possible file formats. The VMS file system is not PC or Unix compatible. Typing DIR/FULL <filename> will show the major file attributes. The bulk of the VMS documentation is available online from HP. Sincerely, Robert F. Thomas 44 Industrial Way Norwood, MA USA 02062 N Office Phone - (781) 329-9200 O mail to: r...@asthomas.com _______________________________________________ Simh mailing list Simh@trailing-edge.com http://mailman.trailing-edge.com/mailman/listinfo/simh
