| Title: | ACMS comments and questions |
| Notice: | This is not an official software support channel. Kits 5.* |
| Moderator: | CLUSTA::HALL AN |
| Created: | Mon Feb 17 1986 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 4179 |
| Total number of notes: | 15091 |
I would appreciate any insight that anyone may have on a workspace
passing problem that occurs on Alpha. I am getting a fax of the code
so that I can take a look but I believe at this point that the customer
is competent and literate in ACMS and has a real problem. This is what
I have found to date.
-------------------------------------------------------------------
The target of a COBOL initialize statement is a passed workspace in a
procedure server step. The initiialize is performed on the 4th argument
in the workspace list passed from the task. The 3rd argument (workspace)
is also being initialized for the first 12 bytes by the same command.
The customer is using COBOL 2.2 on alpha OpenVMS 6.2, he does not
have the /alignment=padding switch available on this version. This switch
apparently enforces natural alignment calling standards for the Alpha.
Dave Butler...
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 4144.1 | refer to v2.3 of DEC COBOL with/align=padd | CSC32::D_BUTLER | Fri Apr 04 1997 18:58 | 6 | |
This does seem to be an alignment problem. The version of COBOL that
they are using does not support natural alignment for Alpha. They have
sent me portions of their code and debug sessions and they seem OK.
This is either an alignment problem for which I referred them on to
DEC COBOL v2.3, or it is a bug in their code. It certainly exhibits some
strange behaviour.
| |||||
| 4144.2 | You cannot allow natural alignment for wsp's on Alpha | CLUSTA::HALL | Bill Hall - ACMS Engineering - ZKO2-2 | Fri Apr 04 1997 19:41 | 11 |
You cannot allow the data to be naturally aligned on Alpha.
ADU generates byte-aligned data structures and cannot be
overridden. If you are passing ACMS workspaces (as defined
in the group/task definition), then you must compile them
in whatever language with the equivalen of /NOALIGNMENT
(sometimes called /NOMEMBER_ALIGNMENT). This is documented
in the ACMS Migration Guide.
Bill
| |||||