Home > IT Answers > AS/400 > Is it possible to disable running of macros on client access centrally as is done in case of DTF’s
JohnsonMumbai
1,160 pts.
 Is it possible to disable running of macros on client access centrally as is done in case of DTF’s
AS/400, AS/400 macros, Client Access, DTF
Is it possible to disable running of macros on client access workstation by running a command centrally as is done in case of DTF's

Software/Hardware used:
ASKED: November 6, 2009  5:40 AM
UPDATED: June 14, 2010  6:23 AM
RELATED QUESTIONS
Answer Wiki:
I don't know if this will disable the ability to run macros but this technique removes a lot of worries for us. We only install Client Access .CAB files 1, 2, and 9. This gives our users all the power they need including mapping to drives on the IFS. If you look at the group of files in your Client Access installation folder you will see a group of file with the .CAB extension. We simply delete all .cab files except 1, 2, and 9, then run the install. My info is based on V5R2 .cab files. Some files added since then. In the five plus years, none of our users have needed any functions beyond what is provided in those three files.
Last Wiki Answer Submitted:  November 6, 2009  4:23 pm  by  WoodEngineer   5,525 pts.
All Answer Wiki Contributors:  WoodEngineer   5,525 pts.
To see all answers submitted to the Answer Wiki: View Answer History.


RSS - Discussions Help
Discuss This Question:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

 

Macros can be either System i macros or VBScript macros.

VBScript macros can be blocked by having these lines in the .WS file:



The 

The lines can be added by any text editor. I've never tried, but I assume that .WS files can be distributed. so that standardized settings are available.


However, the same setting will not affect System i Access macro-language macros. So far, I haven't run across anything that blocks that capability. Only thing I've seen that is related is simply deleting the .MAC files from ./Emulator/Private (where './' is the System i Access directory on the PC.)


I suppose you could execute STRPCCMD in initial programs to cause .MAC files to be deleted at every logon...?


Tom
TomLiotta
 108,055 pts.
 

Ah, sheesh… What’s happened to the editor now? The lines should be (if they work):



We'll see when I click <Add>...


Tom
TomLiotta
 108,055 pts.
 

Okay, it’s not letting “CODE” lines come across for this.

The first line is the letters “API” in square brackets. The brackets are probably messing up the editor. The second line is “PcCodePage=1252″. And the final line is “DDE/HLL=Y”.

Three lines total — the last line turns the API feature on or off.

You can Edit-> Preferences-> API… in a workstation session to add the lines to the .WS session. Then, File-> Save to cause the new setting to be saved. Once saved, open the .WS file with Notepad to see what was added.

Tom

TomLiotta
 108,055 pts.
 

Thanks Tom it worked.

This would have to be done on each pc. However would there be any way by which we can control it centrally on iseries.

Also any way by which we can allow only certain macros to run while not allow other macros.

JohnsonMumbai
 1,160 pts.
 

Is it possible to permanently disable the API

JohnsonMumbai
 1,160 pts.
 

Hi Tom,

The objective is to prevent users from creating another workstation on his pc as earlier workstation parameters are saved and we do not want user to have fresh set of workstation with default parameters as parameters such as within API section to be would get modified.

Hope you have understood.

JohnsonMumbai
 1,160 pts.