| Author |
ODS-5 with long filenames... |
JonathanBelanger
Member
Posts: 42
Joined: 09.06.16 |
| Posted on July 09 2016 11:29 |
|
|
Hello,
I have OpenVMS VAX 7.3 running on a modified VAX SimH emulator (getting 21.9 VUPS instead of the non-modified 19.3 VUPS). On one of my drives, not the system disk, I enabled ODS-5. Apparently this does not automatically support longer file names. How do I get filenames greater than 32 characters on OpenVMS VAX?
Thanks,
JonBelanger |
|
|
| Author |
RE: ODS-5 with long filenames... |
Bruce Claremont
Member
Posts: 623
Joined: 07.01.10 |
| Posted on July 10 2016 08:00 |
|
|
|
According to the documentation (http://h71000.www7.hp.com/doc/82final/5841/5841pro_081.html), long file name support is a Alpha/I64 OpenVMS feature. Spin yourself up a FreeAXP Alpha system to resolve the issue. |
|
|
| Author |
RE: ODS-5 with long filenames... |
malmberg
Moderator
Posts: 530
Joined: 15.04.08 |
| Posted on July 15 2016 08:33 |
|
|
On OpenVMS/VAX you do not even have the option of enabling ODS-5 support on a disk.
An ODS-5 disk must be initialized on a AXP/IA64 system of new enough OpenVMS.
How did you modify VAX/SimH to get higher VUP rates?
I know there is an older fork that allowed multiple CPUs. It needs N+1 for linux so you need at least 3 CPUs to make it worth while. When I tested that fork, the SimH/Idle did not work.
|
|
|
| Author |
RE: ODS-5 with long filenames... |
JonathanBelanger
Member
Posts: 42
Joined: 09.06.16 |
| Posted on July 17 2016 17:48 |
|
|
Yes, you can enable ODS-5 on a VAX (from show device/full):
Disk $1$DUC2: (CANTH), device type RA82, is online, mounted, file-oriented
device, shareable, served to cluster via MSCP Server, error logging is
enabled.
Error count 0 Operations completed 1330
Owner process "" Owner UIC [SYSTEM]
Owner process ID 00000000 Dev Prot S:RWPL,O:RWPL,G:R,W
Reference count 1 Default buffer size 512
Total blocks 8003584 Sectors per track 57
Total cylinders 9361 Tracks per cylinder 15
Allocation class 1
Volume label "SYS$OLDKITS" Relative volume number 0
Cluster size 8 Transaction count 1
Free blocks 1393040 Maximum files allowed 444643
Extend quantity 5 Mount count 1
Mount status System Cache name "_$1$DUA0:XQPCACHE"
Extent cache size 64 Maximum blocks in extent cache 139304
File ID cache size 64 Blocks currently in extent cache 0
Quota cache size 0 Maximum buffers in FCP cache 1375
Volume owner UIC [SYSTEM] Vol Prot S:RWCD,O:RWCD,G:RWCD,W:RWCD
Volume Status: ODS-5, subject to mount verification, file high-water marking,
write-back caching enabled.
~Jon.
Now my problem is that t |
|
|
| Author |
RE: ODS-5 with long filenames... |
malmberg
Moderator
Posts: 530
Joined: 15.04.08 |
| Posted on July 23 2016 08:51 |
|
|
ODS-5 volumes can be mounted on the last versions of OpenVMS/VAX.
RMS can only see the filenames that comply with ODS-5.
There are some tricks that can be done. LIB$FID_TO_NAME or bypassing RMS can allow some access to the otherwise invisible files.
|
|
|
| Author |
RE: ODS-5 with long filenames... |
JonathanBelanger
Member
Posts: 42
Joined: 09.06.16 |
| Posted on August 01 2016 11:41 |
|
|
I reverted back to ODS-2 by creating a new disk that was ODS-2 then using ZIP/UNZIP to move the files from the old ODS-5 disk to the ODS-2 disk. I then re-initialized the original disk back to ODS-2.
Now for my next problem. When I attempted to create a saveset of the ODS-5 and then use the /CONVERT qualifier on the restore, I got an "unrecognized qualifier /CONVERT" error. Help BACKUP_Command shows the qualifier, but the DCL Tables don't recognize it. What do I need to do to be able to CONVERT the restore of a backup from a saveset containing ODS-5 files to an ODS-2 disk drive?
~Jon. |
|
|
| Author |
RE: ODS-5 with long filenames... |
malmberg
Moderator
Posts: 530
Joined: 15.04.08 |
| Posted on August 10 2016 07:44 |
|
|
The help text should indicate that the qualifier does not work on VAX. If it does not, it is a bug.
As stated in the other thread, I was very unimpressed with what backup/convert did, and forgot to mention, it took a very long time before it failed for me because it unexpectedly ran out of disk space, and I had more than enough disk space to manually do the ODS-5 to ODS-2 conversion. |
|
|
