MNUCMD

Menu-Driven Application uses MNUCMD files to bind a menu, a MNUDDS source file, selection to an action like to call a program.

Call

CALL statement implies dependency on the program named PROGRAM_ID in the project.

CALL PROGRAM_ID
CALL PGM(PROGRAM_ID)

Change Data

CHGDTA statement implies dependencies on source files named FILE2_ID and FILE_ID in the project.

CHGDTA DFUPGM(QALIB/FILE2_ID) FILE(QADATA/FILE_ID)

Clear Physical File Member

CLRPFM statement implies dependency on the source file named FILE_ID in the project.

CLRPFM FILE_ID

GO statement implies dependency on the source file named FILE_ID in the project.

GO MENU(FILE_ID)

Run Query

RUNQRY statement implies dependencies on source files named FILE2_ID and FILE_ID in the project.

RUNQRY QRY(QALIB/FILE_ID)
RUNQRY QRY(FILE_ID) QRYFILE(*CURLIB/FILE2_ID)

Submit Job

SBMJOB statement implies dependency on the source file named FILE_ID in the project.

SBMJOB CMD(CALL PGM(CIS400/FILE_ID))

Display File

On AS/400, a utility called SDA (Screen Design Aid) to easily create a menu. The utility will create several files for menu with the same name. Based on the naming convention, a dependency link "Display file" will be formed between the mnucmd file and mnudds file.

Example: Let's consider the menu with name 'CARDMENU' is created with help of SDA. Then, CARDMENUQQ.mnucmd, CARDMENU.mnudds, CARDMENU.msgf, CARDMENU.pnlgrp files will be generated. In this case, dependency of link 'Display file' will be established between CARDMENUQQ.mnucmd and CARDMENU.mnudds.