New features added, version 7.5.2, 7.5.3, 8.1, 7.5.4, 8.4, 8.5.1, 8.5.2,
Program MUJM, Menu and Job Parameter Maintenance, is used to enter and maintain application types, menu definitions, program definitions, menu selection orders, program job definitions, program conflicts and missing job definitions. You can also display program types, program conflict types, and process types.
When a program has the Query Mode Action pop-list set to Internal Use and a user tries to run the program, a warning box is displayed stating that there is no such program and to try again.
Entries in this program are color coded based on their function:
Black designates menus.
Red designates reports and jobstreams with reports as the first entry.
Green designates SQL processes and jobstreams.
Blue designates maintenance, transaction, and inquiry screens.
Purple designates web applications, Xephr applications, and other entries that do not fall under the other four colors.
Creating New Application Entries
Entering Pre-Set Report Parameters
Default Report Parameters for Jobstreams
Querying Missing Job Definitions - Missing Job Defs Tab
1. If you are using a new application type, you must first enter the application type on the Application Types Tab. The application type code is the module within which menus and programs will be classified on subsequent tabs. It is used to determine system security with program MUSC, User Security Maintenance.
Set the custom entry flag to on if this is a custom application type. Upgrades will not overwrite application types with this flag set to on.
2. If you are entering the program in a new menu, create the menu on the Menu Definitions Tab. Most often, however, you will be adding a program to an existing menu.
Set the custom flag to on if this is a custom menu. Upgrades will not overwrite menus with this flag set to on.
3. Go to the Program Definitions Tab.
4. In the Menu Option field, enter the name of the program as it will appear on the menu.
5. In the App field, enter the application type from the Application Types Tab. The application type is the application module within which the menu option appears.
6. In the Typ field enter the program process type. The following is a list of the possible program process types that can be assigned.
3 SQL*Plus
Program
5 (Job +Ok prompt +Screen Heading)
6 (Job - Ok prompt -Screen Heading)
20 Oracle Reports 2.0 Program
30 Discoverer Reports
40 Forms 4.0 Program
50 Web Program
60 Xephr Program
70 Menu Option
*If
you enter 5 or 6 in this field, then the program name will be automatically
populated with 'job'.
*If
you enter 20, in this field, then a job record will be automatically inserted
in the Job Definitions tab.
*If
you are on the Program Definitions tab and the Type is 20 or the Program
Name is 'job', the program will be auto queried when clicking on the Job
Definitions tab.
*If
you are using the Emailing Reports from the Jobstream feature, the Typ
field must be 5, 6, or 20.
*Menu
Option allows you to run another program as if you had typed that program
name in at the menu.
For example, the FAGJ menu option runs program GLGJ, Move Generic
GL Interface Journal Transactions, but FAGJ is included on the menu for
Fixed Assets.
7. In the Conf field enter 0. Conflicts are no longer used by NDS Applications.
8. In the Query Mode Action field, choose the query mode that can be used for the program. Forms programs will always be No Query Users, Use as Maint, or Always Query. Non-forms programs (e.g. Reports & Processes) can be No Query Users or Query Users OK. System values are as follows:
No Query Users This program cannot be run by a query only user.
Use as Maint This program is always run in maintenance mode even for a query only user.
Always Query This program is always run in Query Mode, whether user is a maintenance user or a query user.
Query Users OK This is a report or a form that is OK for query only users to run. Forms will be in query mode only.
9. In the Menu field, enter the menu from the Menu Definitions Tab on which this program is listed. The menu entered here is also the menu that will be displayed on your screen after the program has run to completion.
10. In the Title field, enter the program description that will be displayed on the menu for the program.
11. In the Program Name field, enter the program pathname. If the program runs a job which will be defines on the Job Definitions Tab, enter job here (must be in lower case).
If the Typ field is 60 - Xephr Application, then the program name string is a URL to the Xephr application, including the two tokens, ^LOGIN^ and ^PASSWORD^. At run time, the ^LOGIN^ token is replaced with the operating system login, and the ^PASSWORD^ token is replaced with the hash of the NDS application log in.
You can pass drill down keys and values from program UTKM, Maintain Drill Down Keys here. List the drill down key and its desired value after the program name. For example, the FAGJ menu option is set up with the program name: glgj JOURNAL_TYPE=ASSETS .
12. Set the Custom Entry flag to on if this is a custom program. Upgrades will not overwrite programs with this flag set to on.
13. Set
the Custom Help flag to on if
this program will open custom help documents instead of standard NDS Applications
help when the [Help] 
button
is pressed.
Some set up is required. For more information, see the NDS Custom Help section.
14. Press [Commit].
16. Enter Query. In the Menu Option field, enter the name of the menu on which the program is to be listed. Execute Query.
17. For the program that you entered, enter the sequence number to indicate where you want the program to be displayed in the menu.
18. Press [Commit].
19. Go to the Job Definitions Tab if a job sequence was auto created or needs to be entered for the program. Job definition entries are required for program types 3, 4, 5, 6, 7, 8, 9, and 11 for which program definitions were entered on the Program Definitions Tab. These are the programs for which you entered job in the program name field.
20. In the Menu Option field, enter the program name that is displayed on the menu. When the program is run from the menu, the system will look here for the jobstream of the program.
21. In the Menu Opt Seq field, enter the sequence number that indicates when the menu selection entered below will run in this jobstream.
22. Set the Ok to run flag to on or off to indicate if user should be asked for confirmation before running this job. If set to on, the menu will prompt the user "Is it Ok to run program name?" The program name will be taken from the Popup Title field (re-titled from Screen Head field in 85R1).
23. In the Seq On Success field, enter the Menu Opt sequence number to run when this job completes successfully: (0 = end).
24. In the Seq On Error field, enter the Menu Opt sequence number to run if this job terminates abnormally: (0 = end).
25. In the Seq On Not OK field enter the Menu Opt sequence number to run if the user chooses not to run this job by selecting No at the OK to run prompt: (0 = end)
26. In the Menu Selc field, enter the program that will be run at this point in the jobstream.
27. In the Prog Type field, enter the process type for the program. See step five above for a list of process types.
28. In version 85R1, the Report Engine Native Mode flag has been replaced by the mode field on the MUPM, Printer Definition Maintenance form. The valid choices there are Default, BitMap or Character and are now linked to the printer rather than the report.
29.In the Rpt Orientation field, if the program in the Menu Selc field is a portrait report, choose Portrait (132 characters). If it is a landscape report, choose Landscape (160 characters). If the menu selection is not a report, leave the field blank.
30. If you are entering a report and have .prt file for the report that is not one of the standard .prt files that come with the system, enter the .prt file here.
31. In the Report Class field, if the program in the Menu Selc field is assigned to a report class, enter the report class here.
If you are generating a report to be emailed from the job stream, enter GENERIC as the report class here. For more information, see Emailing Reports from the Jobstream.
32. In the Ovrd Printer field, if you wish to have one specific printer always print the report, enter the printer name, as entered in program MUPM, Printer Definition Maintenance, in this field. The report will always print to this printer, no matter what the printer field on the menu displays. The printer should be selected from the List of Values in this field.
33. If you are entering a report, and you do not want the runtime parameter form to be displayed before the report prints, you should set the Display Form flag to off. You should never set the flag to off for reports that have parameters that are required to be entered before the report prints.
34. If you are entering a report and you want the report to be generated and emailed to a specific email address, in the Rpt Email field, enter the email address. For more information, see Emailing Reports from the Jobstream.
35. In the Prog Name field, enter the program pathname for the program in the Menu Selc field.
You can pass drill down keys and values from program UTKM, Maintain Drill Down Keys here. List the drill down key and its desired value after the program name. For example: glgj JOURNAL_TYPE=ASSETS .
For reports without job streams, you can pass report parameters here as well. For more information, see Default Report Parameters for Jobstreams
36. In the Scrn Head field, enter the menu title of the program from the Program Definitions Tab.
37. In the Job Args field enter additional command line arguments that are passed on to the command line for job types 3 and 4 at run time. You can also enter pre-set parameters for reports in this field.
For reports with job streams, you can pass report parameters to the report here as well. For more information, see Default Report Parameters for Jobstreams
Examples for additional command line arguments:
Program UTMS passes job arguments %uid 2&>dev/null &
%uid is a placeholder the menu system substitutes the user id and password for the %uid
2&>dev/nul & Take UNIX file streams with handles 1 & 2 and redirect the output to the null device and detach the process.
Program BULUM and BULUR run the same program but BULUM passes Argument 0 while BULUR passes Argument 1 which tells the program which mode to operate in when different options are selected at run time.
%term is a placeholder for the terminal type used for report display only
%useq is a placeholder for the user's log-in id #. The menu assigns the user a log in id number when they sign on to the system. This is stored as part of a file name in the temp directory. It is used by some background and job processes and to uniquely identify reports created by the user as part of the unique report ID.
Job Arguments can be used to temporarily run the program in debug. An example to run APCU in debug and direct to a file named apcu.dbg would be:
-1d >apcu.dbg
37. Set the custom entry flag to on if this is a custom jobstream for this program. Upgrades will not overwrite programs with this flag set to on.
38. You can enter SQL text to be run for the jobstream. The system will run the SQL text entered here before running the job step.
The SQL text entered in this field should return a number.
If the number returned is 0, the job step will not be run.
If the number returned is anything other than 0, the job step will be run.
The Seq on Success sequence number will be run if the number returned is 0, or if the SQL text is invalid.
39. Repeat steps 18 through 38 until you have entered the entire jobstream for the program.
40. The Conflicts Tab deals with program conflicts within NDS Applications. Program conflicts are no longer used by NDS Applications. Do not enter program conflicts as they will not work.
41. See the Querying Missing Job Definitions - Missing Job Defs Tab section for information on querying missing job definitions on the Missing Job Defs Tab.
Pre-Set Report Parameters can be set up in this program so that when a report is run, the desired parameters are entered automatically and the user does not have to enter then when the Report Parameter Form is displayed. If pre-set parameters are set up in this program for a report with the Display Form flag set to off, the parameters will still be entered automatically and the report will be printed according to the pre-set parameters.
Pre-set parameters are entered in the Job Args field for the report.
1. To set up this feature, you must first determine the required parameters for the report. This information is displayed in program UTKM, Maintain Drill Down Keys.
2. In program UTKM, Maintain Drill Down Keys, query the report for which you wish to enter pre-set parameters. Each drill down key is a parameter for the report.
For example, program OEPRL, Sales Order Pick List (Laser), has two parameters in program UTKM, Maintain Drill Down Keys - P_PLANT_CODE and SALES_ORDER_NO.
Program APAH, AP Historical History Report, has four parameters in program UTKM, Maintain Drill Down Keys - START_DATE, END_DATE, START_VENDOR, and END_VENDOR.
3. Once you have determined the report parameters, you can set them in program MUJM, Menu and Job Parameter Maintenance.
4. Query the desired report on the Job Definitions Tab in program MUJM, Menu and Job Parameter Maintenance.
5. If there is a jobstream for the report, find the entry with the Proc Type of 20. This is the actual report.
6. In the Job Args field, enter the parameters and parameter settings for the report, with the parameter and its setting separated by an equal sign. If there are multiple parameters, separate them by a comma.
For example, for program OEPRL, Sales Order Pick List (Laser), you could enter the following to set the plant code to 20: P_PLANT_CODE=20
For program APAH, AP Historical History Report, you could set the dates and vendors as follows: START_DATE=01-01-01,END_DATE=03-01- 01,START_VENDOR=1,END_VENDOR=6
8. Press [Commit].
9. When the report is run, the parameters will be entered on the Report Parameter Form, and can be changed by the user, if desired.
10. If the Display Form flag is set to off, the report will be printed for the pre-set parameters.
Reports can be set up so that report parameters default in the parameter form. There are two ways to do this.
If there is no job stream for the report, the parameters are listed after the program name in the Prog Name field on the Program Definitions Tab or the Job Definitions Tab.
If there is a job stream for the report, the parameters are listed in the Job Args field of the job sequence that runs the report itself on the Job Definitions Tab.
Arguments must be separated by commas.
If the argument matches a drill down key for the report in program UTKM, Maintain Drill Down Keys, the drill down key will also be set.
If the argument does not match a drill down key in program UTKM, Maintain Drill Down Keys, the parameter will be set, but if the parameter doesn't actually exist on the report, you will receive an error when the report is run.
Standard date substitution variable can be entered in the list or arguments in order to have the report date parameters automatically default when the report is run.
All substitution variables are based on the current system date and must be surrounded by the carat character ^
^EOM^ -- last day of current fiscal period
^FOM^ -- first day of current fiscal period
^EOY^ -- last day of current fiscal year
^FOY^ -- first day of current fiscal year
^LEOM^ -- last day of previous fiscal period
^LFOM^ -- first day of previous fiscal period
^LEOY^ -- last day of previous fiscal year
^LFOY^ -- first day of previous fiscal year
^SYSDATE^ -- current system
date
Days can be added or subtracted from system date in the variable. For
example: ^SYSDATE-1^
Custom substitution variables can be set up. Contact your NDS Project Manager for more information.
Program APGL, Detail AP to GL Distribution Detail Report, has LODATE and HIDATE parameters in program UTKM, Maintain Drill Down Keys.
To have the report always
run for the month to date, the Job Arg field for the report on
the Job Definitions Tab could be set to
LODATE=^FOM^, HIDATE=^SYSDATE^
If there is no job stream
then the Prog Name could be set to:
apgl LODATE=^FOM^, HIDATE=^SYSDATE^
Program PMLBD, Labor Detail Time Report, has STARTEMPNO, ENDEMPNO, STARTDATE, and ENDDATE parameters in program UTKM, Maintain Drill Down Keys.
A special menu option
for an employee could be set up to run the report and default the
parameters to meet that employee's needs.
In the Prog Name field for the menu option on the Job Definitions Tab,
the following could be entered:
pmlbd STARTEMPNO=ME, ENDEMPNO=ME, STARTDATE=^SYSDATE-7^ ENDDATE=^SYSDATE^
Often-used web sites and email can now be activated from the NDS Menu system. After the menu options have been set up in this program, you can just double click on the menu option.
1. On the Program Definitions Tab, enter the menu option that you wish to assign to the web site or email address.
2. Enter the application type in the App field. The application type is the application module within which the menu option appears.
3. In the Typ field, enter 50 to indicate that this is a web program.
4. Enter 0 in the Conf field.
5. Set the Query Mode Action pop-list to No Query Users.
6. In the Menu Field, enter the Menu on which you want this web program to appear. The standard NDS menu is EIW.
7. In the Title field, enter a title for the web program. For example, if you were creating a link to the NDS home page, you would enter NDS Systems' Home Page in this field.
8. In the Program Name field, enter the link to the desired web action.
For web pages, you would enter the URL here, preceded by http://. For example, a link to the NDS home page would be http://www.ndsapps.com
For email addresses, you would enter mailto: followed by the email address. Or, if you just wanted a blank email to be opened, you would simply enter mailto: here.
9. Set the Custom flag to on to prevent your menu entry from being overwritten in later upgrades.
10. Press [Commit].
The program name contains the script to run (including path) and any variables passed to the script separated by commas (no spaces allowed). For example: path\myscript,var1,var2,var3. The path and the script must exist on the app server because that is where the command tool shell will be opened by the host command.
The script must have the same number of variables defined as passed and the variables must be numeric. Up to 5 substitute variables (&1 thru &5) can be passed using drilldown keys.
The example below uses a drilldown key for the second variable in the script (actually defined in the script as '&2' so there is no relation naming wise between the drilldown variables and the script variables).
The script MUST have an 'exit;' at the end of it or your session will hang.
UTKM Setup, drilldown key#1 equates to '&1' in the program name in MUJM.
Drilldown set up in UTCV to run the script.
The programs displayed on this tab are those with valid program definitions on the Program Definitions Tab that do not have a job definition set up on the Job Definitions Tab. Program types of 3, 4, 5,6,7 and 20 also required a job definition.
1. Press [Execute Query].
2. All programs that have been set up on the Program Definitions Tab with a type of 3, 4, 5, 6, 7, or 20 that do not have a corresponding job definition on the Job Definitions Tab will be displayed.
3. If the Program Definition is set up with a type of 20 and there is no job definition, the system will attempt to run the report by looking on the Program Definitions tab. If the report will still not run, correct by following step 4 below.
4. Correct the problem by entering a job definition for the program on the Job Definitions Tab.
Press this button to insert a gap in the jobstream sequence before this sequence. This sequence and those after it will be renumbered by 1.
Press this button to re-sequence job streams by 1 and remove gaps. This can be done at any point in the job stream. Message will be posted at bottom in gray bar Gaps Removed. See UTDB for previous job definition. The before job stream is automatically streamed to UTDB for reference, if done using this button.