I haven't used UV in a while. When I had to convert a D3 account to Universe, there were specific tools to do it. 

I can't find them now under Windows and UV 12.2. 

The documentation mentions tapein routines or using the import command under Xadmin. Everything is incomplete.

Under D3 windows I created a tape pseudo device, set the block size to 512 and used the 'SAVE (TIC" command to create an individual account save that is backwardly compatible.

UV documentation has no mention on how to create an entry in the &DEVICE& file to access a windows disk file.

Sorting through the VOC verbs I found a command D3RESTORE which looked promising but is not in help system or other documentation.

When I used the command  D3restore INFILE "D3ACCOUNT" I get an error

"Error Occured at Input Byte: 13"

Any help would be appreciated.

I haven't used UV in a while. When I had to convert a D3 account to Universe, there were specific tools to do it. 

I can't find them now under Windows and UV 12.2. 

The documentation mentions tapein routines or using the import command under Xadmin. Everything is incomplete.

Under D3 windows I created a tape pseudo device, set the block size to 512 and used the 'SAVE (TIC" command to create an individual account save that is backwardly compatible.

UV documentation has no mention on how to create an entry in the &DEVICE& file to access a windows disk file.

Sorting through the VOC verbs I found a command D3RESTORE which looked promising but is not in help system or other documentation.

When I used the command  D3restore INFILE "D3ACCOUNT" I get an error

"Error Occured at Input Byte: 13"

Any help would be appreciated.

David,

To access a disk image of a virtual tape you can create a tape device using the MOTIF menus in the UV account on UNIX or XAdmin on both UNIX and just enter the path to the file as the device. I seem to remember there was a limit to the character length of the path in MOTIF, so keep the path relatively short or manually edit an MTn record in &DEVICE& as needed. Alternatively use XAdmin. I must admit hat I tended to manually edit &DEVICE& myself, using MT0 as a template in the past. For a disk file the rewind and non-rewind devices are the same.

If the tape account save is in legacy pick format then acct.restore I think will work, otherwise it's worth opening a ticket with Support.

Regards

JJ.

David,

It has been a while since I wrote D3RESTORE.

There are a number of parameters available to the D3RESTORE command. 

RUN APP.PROGS D3RESTORE -H

Command: D3 {Keyword value} ...
Command Keywords and arguments:
INFILE INFILE
SIZEBLOCK 512
SIZEHEADER 512
SIZELABEL 80
SKIPONCE 1536
SKIPEACH 12
VERBOSITY 0

Since you set the block size to 512, you may need to set SKIPEACH to 0, Normally, D3 skips the first 12 bytes of each block - a throwback to the 512 byte blocks, the idea that computers should run in decimal as people think instead of binary, and at the end of an account there is EOF text to indicate if there is a following account.

If you are running a UNIX variant, the command "od -xc -Ad AccountSaveFile | head -100" should provide enough detail to taiior the D3RESTORE command arguments

The errors are strange Extranious character 1, seq(49) found at bite 13.

The label, the first 80 characters:

L 0200 20:51:04  10 Aug 2023 203051 DATA                                    ~01

really confusing. do remember what the Verbosity settings are?

I had the program work once. but beats me how that happened. I can't replicate it.

Did you try it with  SKIPEACH set to 0? It looks like SIZELABEL is correct at 80.

You did supply what looks to be the first 80 characters, but the command I requested would provide a better examination of the data and the 100 lines would have been a display of approximately 32K, which would help with some of the other settings.

I know, but I am running Windows, not Unix. I should have been clearer. I was lamenting that things work better in Unix but this is a Windows Server setup.

I think this is what I am looking for. Actual save label starts as A01 or 2561?