Register a new procedure using adccm in LAS
A newly created procedure cannot simply be typed into the LAS command prompt before LAS knows about the command.
The procedure must first be registered using the LAS command-maintenance functionality.
There is an existing LAS/OpenEdge command-maintenance program that you invoke from the LAS environment i,e:
adccm ,which opens a screen titled:
ADD/CHANGE A COMMAND
And then you need to click Y to proceed.After which, you need to fill the details related to your procedure in the screen showing up such as :
For example if your procedure name is location.p.
| COMMAND: | location.p |
| SYSTEM | SYS |
| SUBSYSTEM | LAS |
| GROUP | |
| TYPE | |
| INCLUDE | N |
| INDEPENDENT | N |
| BATCHABLE | N |
| AUTO PRT: | N |
| PRINT TIMES: | 2 |
| PRT STYLE: | POTRAIT |
| DEL PRT: | N |
| DESC | Location report |
Once the procedure has been registered using adccm, LAS can recognize the procedure as a valid command.
The next step is to test the procedure directly from the LAS command prompt.
For example:
Command: location.p
LAS should then start the new procedure.
This is an important Proof of Concept milestone.
The test confirms that:
- The procedure exists.
- LAS knows about the procedure.
- The LAS command registration is correct.
- LAS can locate and execute the procedure.
- The procedure can operate within the normal LAS session.
Conclusion
Adding a new procedure to LAS involves more than creating a Progress .p file.
The procedure must move through three stages:
Development → Command Registration → Menu Integration
The critical point is that command registration must occur before the procedure can be called by name from the LAS command prompt.
The adccm utility provides the mechanism to register the procedure with LAS. Once registered, the procedure can be tested directly from the LAS command prompt. After the procedure has been validated, it can then be added as a permanent option to the appropriate LAS menu.
For a new procedure such as location.p, this approach provides a controlled and repeatable path from initial development to a fully integrated LAS menu function.
Abotts Partners with singapore based tech giant to help migrate their public sector customer from Sybase to SQL server.
Abotts partners with NYPL to integrate with their partner libraries.
Upworks Inc partners with ABOTTS to build their Oracle Cloud Infrastructure (OCI) and migrate their custom applications to OCI.
Abotts Inc Partners with Gnorth consulting to deploy exadata and ODA for a large public sector customer.