Greetings my fellow Lawsonians....

Lawson v8 on HP UNIX v11.11.

I am curious on if there is a way to remove self service accounts (RD30 records from a command line or calling an API...

other than lapm productline RD30? Are you looking for a batch solution?

Sorry for the lack of Lawson terminology...

What I (by I - I mean my programmer) I would like to automate the process of removing the RD30 record (Self Service account).

Right now our programmer has automated the de-activation of Active Directory accounts by looking in Lawson at an employees "Status".

If the status of an employee changes to T1/ T2/ T3 the program will disable the Active Directory account of the employee.

What I would am looking for is for our programmer to create a program that I can type the employee's "Employee Number" in and have it remove the terminated employee's Self-Service (RD30)?

The manual process is:
From the Lawson "terminal" program: "UNIVWIN.EXE".
Command:
lapm logan rd30
I type the Id in: example: jsmith
I click on "More Information" tab; click on "Mult Attribute Types" button; click the delete button at the top of the screen.

This is why I was asking about an "API".

Thank you in advance for any help you can provide.

RD30's are kept in a table so technically your programmer could write a script or program to delete the records based on employee status.

You can use and AGS call to do this pretty easily.

Hi - A shell script would work great. We developed one that created csv files to delete from rd30. The file is then emailed (within the script) to a superuser. Then they would open the file and use MS-ADDINS and upload to delete the RD30 recs. The file was pre-formatted in the script for MS-ADDINS and we setup a template to use for the files.

The script internals basically use rngdump on the employee field for your Termed employees. Then use another rngdump on logan. Then do a diff between the 2 files for records in the logan file that are NOT in the employee file. The results of the diff are then inputted in a file that you will use MS-addins to delete the RD30 recs.

The script also deleted our Apache userid accounts.

You can automate the deletes in the script with an ags call, but our superusers in the various business units wanted to control that.

Thanks,
Mark

Can anyone tell me if there are any manuals or books for Lawson programming?

By Lawson programming, what do you mean? Lawson's environment is a complex layered mashup of many different technologies developed over many years. I can give you an answer for the one part that I know well enough, the COBOL side, used for UNIX/Windows. 3 main sources:
- Need to know COBOL a bit. There are a number of COBOL manuals on-line. the 'flavor' of COBOL that Lawson uses is MFC - Micro Focus COBOL
- Look at the Lawson Source Code. You'll see "how it's done'. If you screen-paint a program and then 'Generate' it, you'll be able to see how a Lawson program is built out of the fields you painted
- Check Lawson's API manual It includes small code examples

(If you're using IBM's I-series, then I believe that you're going to have to refer to RPG instead of COBOL. I don't have any experience in it.)

Then there's Design Studio, Lawson Add-Ins, DME calls, and on and on it goes ... sorry I can't comment on those, I really don't know enough about them. Each of those other 'programming' environments needs further skills, like knowledge of javascript for Design Studio, etc.

Thanks Milo -

I guess I was referring more to the "Lawson's API manual".

I personally am not a programmer but the company I work for has one that is going to do the programming for me. I am trying to gather some information for her.

Do you know if an I get the Lawson's API manual online from Lawson? I think that will help her.

Yes, Lawson's API manual is online at the Lawson Support Site. Search the Documentation link. Two "caveat emptor"'s to watch out for:

1) Make certain you're downloading the manual for the correct version # and OS.

2) Be aware that the API manual is not guaranteed 100% accurate. I have seen prior versions where something listed didn't work. A later version of the API manual then mentioned that the feature was never implemented. So - test everything that you see! (If what you see is what you find in the source code, then, it works!)

One note of caution when programming COBOL - the equivalent of the case statement in COBOL is not implemented. I believe it's the SWITCH command. In the past, I searched & tried to reinstate it, just for my own purposes (since I don't think it would affect Lawson's code) but have not been able to figure out how Lawson disabled it in MicroFocus COBOL. Why they did that, I don't know -- because they also use some highly advanced object-oriented style constructs. Oh well.

Oh, one more thing ... you may also want to get that programmer the Application Development Workbench (ADW) and ADW Standards guides. Those 2 are very important to understand the screens and reports and how they work. (The screens and reports form a layer of code that is compiled separately, not with the COBOL compiler.) Again, make sure you get the right version # and OS.