We're running AREV 3.12. I hadn't used the BATCHUPDATE process before. From TCL, F10, Utilities, Developer, Batch. When I selected the Batch menu item, I got the message W549 'The "DICT BATCHUPDATE" table is not available.'. Sure enough, we don't have a dictionary for that table. Can anyone suggest how I should go about getting the Batch process to work? Is the DICT.BATCHUPDATE table supposed to have any real, symbolic or group definitions or should it be empty? Do I just need to recreate the BATCHUPDATE table?

Thank you for your time.

Michael Slack

Try this (from an ArevDOS 3.12):

FMC NAME S/M JUST LEN

0 UNAME S L 10

1 UFILE S L 10

2 UFILTER S L 10

3 UFILTER.TXT S L 10

4 UFILE S L 10

5 UFIELD M L 10

6 UFORMULA M L 10

Hello Dave:

Am I correct in assuming that these are the dictionary definitions for the BATCHUPDATE table? So, I should delete the BATCHUPDATE data table (sorry I forgot to mention I had that) and recreate the data and dictionary tables from scratch?

Thanks,

Michael Slack

The column name UFILE is list twice (FMC 1 & 4). Since these are the record ids they should be unique.

FMC 4 should be named UTFILE

You can create just the dictionary in Arev32,

I'd create it while in the SYSPROG application:

MAKETABLE REVBOOT DICT BATCHUPDATE

You will have to then add it using the OI Database Manager.

Then rename it to be GLOBAL using the OI Database Manager.

Dave

Hello Dave:

I don't know if this matters or not but I'm working in AREV 3.12 and not OI AREV32.

Thanks,

Mike

Not at all, just do the MAKETABLE, then do a RENAMETABLE to make the dictionary GLOBAL.

Dave

Thanks. Every copy of 3.12 I've seen is missing this dictionary. I think it got missed in the upgrade process but is there in the full 3.12 installs.

Hello Dave:

I finally had a little free time to implement your information. It now works. At least when I select the BATCH menu item, it brings up the BATCH window and not the error message. I haven't had time to go further.

One thing I found in my environment is that the data table for BATCHUPDATE is local to the application. That allowed me to delete the table and recreate it from scratch with the dictionary definitions you gave me. I like the idea of making it GLOBAL. But that is for another day.

Thank you for all of your help.

Michael Slack

It was customary for the dictionary files of system tools like BATCHUPDATE, MENUS, POPUPS, … to be GLOBAL, and the data file for

the tool to be assigned to the Application in use.

Dave

View this thread on the forum...