[RESOLVED] How is the data in the ACMS Workspaces defined so it can be passed to the tasks?

« Back to Previous Page
1
0
RESOLVED
Posted by kbarnes (Questions: 4, Answers: 11)
Asked on March 2, 2016 2:59 pm
Category: VMS Software Inc.
263 views
0

OK, Brett Cameron gave the answer I was looking for. Here it is…
The workspace record structures get defined in CDD and these are then referenced in the TDF files (Task Definition). This may seem like a slightly strange way to go about things, but CDD (Common Data Dictionary) then provides a common reference point: COBOL or C code can include those workspace structures, etc.

As you say, workspaces can be passed between tasks, just as you would pass arguments between functions. Essentially, once your inside of ACMS you are just passing around the workspaces as you’d pass around a struct (by reference).

Posted by kbarnes (Questions: 4, Answers: 11)
Answered on March 2, 2016 6:01 pm
0

So, the bottom line is that you are trying to replace an existing legacy application with a more modern platform? If so, please contact me offline as this is not likely to be completely resolved online here. I have participated in such conversions before. While not overly complicated, there are issues that need to be understood about how the legacy system uses these data areas that will determine how the replacement is designed. Shoot me an Email at the address below and I’ll provide more details.

Dan

dansabrservices at yahoo

Posted by Abrsvc (Questions: 0, Answers: 7)
Answered on March 2, 2016 5:22 pm
0

I seem to recall back in the early 80’s that DEC had it’s own, proprietary transmission control protocol… I remember it was one of those 3 character acronyms… which began with R. Sheesh I’m getting old! Anyway, I thought that later on they change ACMS to use either Decnet or TCP/IP. This is something I recall from the late 90’s. I don’t know if these vague recollections help any, Kevin. Maybe it points in the right direction. You might want to ask the OpenVMS on Usenet.

Posted by ElScotso (Questions: 1, Answers: 6)
Answered on March 2, 2016 4:09 pm

You may be thinking of RTR (Reliable transmission router?) which was a connection protocol system. ACMS is Application Control and Management System which was a VAX version of TRAX which ran on PDP11 systems. This was designed for transaction processing and allowed for easy control and management of many ”terminals” using TDMS (Terminal Data Management System) or FMS (Forms Management System) and later DECForms.
Dan

(Abrsvc at March 2, 2016 4:30 pm)

Yes, RTR … You have a far better memory than I do, Dan!

(ElScotso at March 3, 2016 9:17 am)
0

There is really not enough information here to allow me to provide a meaningful answer. Can you better describe what you are trying to accomplish? Also, what language are you using for your application? Most ”data spaces” are defined by the language being used. There are both global and local areas available to applications using ACMS. A better picture of your application requirements should allow me to provide you with a small example using the same language.

Dan

Posted by Abrsvc (Questions: 0, Answers: 7)
Answered on March 2, 2016 3:31 pm

OK, fair enough. I am not looking at a specific language issue as I am interested in the infrastructure used in workspaces. I am looking to transform ACMS applications to a broker based middleware application that is platform independent. As such, I don’t need the global workspaces since they won’t apply to processes in separate address spaces. Language should be irrelevant as I am focused on the data being passed (I am passing numbers as character strings and not IEEE formats). I need to define the data being passed into an IDL so that I can generate client and server stubs for marshalling the data over the wire.

(kbarnes at March 2, 2016 5:15 pm)
« Back to Previous Page