Custom Hooks in SMS100

Does anyone know of documentation for all the custom hooks for SMS100? For instance, currently there is a hook that will perform out to "SMS10A;return_to_menu" anytime the user returns to the menu. Some that I know of are:

SMS10A;return_to_menu
SMS10A;security_check

I would like find one that is performed on the user has logged in and Facts menu screen has been drawn. Also I am looking for a hook that is performed while the screen is still up and Facts is exiting.

Any help you can give would be appreciated.

Thanks,
James
Sequoia Group, Inc.

Find more posts tagged with

Comments

greimer

At least one more that was available: prog/SM/SMS10A;setup_globals

Seems like I knew of others [at one time].

salbritton

James,

From the FACTS 7.5 technical manual, here are some hook points in FACTS 7.5 in SMS100. There are probably more - I know Tim Plotner was rewriting the tech manual for 7.7. Not sure when that will be out, though.

The following exit points are available in SMS100:
Upon returning to the menu, any procedures held in
EXIT_PROC$ and/or EXIT_CUST$ will be performed. They
are considered to be evals, so they must be set with quotes
surrounding them
(e.g.EXIT_CUST$=quo+"custom;procedure"+quo). Also, the
menu driver blanks these variables after performing them, so
the variables must be set by the program that runs SMS100.
These were introduced by the Report Driver, and the fields for
these variables are located in SMRPTS, but you can use these
variables regardless of what program you’re working with.
When initially signing in, after the standard global variables
are set, FACTS performs "prog/SM/SMS10A;setup_globals"
for you to set any custom globals that might be of concern.
Copyright © 1984-2005 Infor, Inc. CONFIDENTIAL 18-13
Exit Points Technical Manual — FACTS 7.50
When the user attempts to select a menu option, FACTS
checks whether the user has security clearance for it. After
checking terminal security and the security codes, the system
performs "prog/SM/SMS10A;security_check". The procedure
has access to all the SMNAME variables (in SMNAME$ for
GUI and in the iolist variables for CUI). The procedure can set
the boolean REJECT_PGM=1, and the user won't be able to
select the program. The custom procedure should issue any
applicable messages - the driver won't provide any UI.
The system calls the program, SMC500, without a call/enter
list while the user is navigating the menu – you have to create
SMC500 and put in an escape to get a feel for when it gets hit,
but it's basically after each action the user takes.
When the CUI menu is about to be displayed, SMS100 read
SMSLCT. Immediately after reading it with the IOLIST,
SMS100 performs SMS10A;read_smslct. At that point, you
have the ability to modify the SMSLCT variables to change the
menu that’s about to be displayed. Be sure you modify all of
the necessary variables (e.g. D2$ and E2$).
When a GUI user first signs in, SMS100 builds an array of the
entire menu structure. Programs and menus that the user
doesn’t have security access to are automatically eliminated
from the menu and are not displayed. As the array is being
built, SMS100 will perform SMS10A;menu_security_check. At
this point, you can set the variable OK=0 if you don’t want the
current program or menu to appear. The SMNAME$ string
template is available to you as the program/menu being
considered.
The custom procedure, prog/SM/SMS10A;get_menu_logo,
can be used to display a different menu bitmap for each
company. In prog/SM/SMS10A;get_menu_logo, simply set
the variable menulogo$ to the name of the bitmap to display.
For example:
get_menu_logo: let menulogo$=”company”+%a0$+”.bmp”
return

Copyright © 2025 Infor. All rights reserved.