A program item folder contains a set of scalars that store information about the program item. Program item folder scalars have both create and read access. Therefore, an application can create a program item folder.
A program item folder has the following scalars:
At Windows and Windows NT computers where this network application is available, this text is used for the application's program item in the Program Manager and for its icon when the icon is minimized on the desktop.
For example, you could specify the name of the application, such as "Microsoft Excel version 5.0."
Specify the file name of the application; the extension is optional. (For example, WINWORD.EXE, WINWORD, VPPROF.BAT, and VPROF will all work.) You can also specify a text editor and a file together, such as NOTEPAD README.TXT.
The command line is run from the package's root directory, which is located on a shared directory on a server.
Caution Your application must set at least one platform flag for the Platform flags scalar. If your application does not set a platform flag, the program item will not be available for program groups. To correct this problem, your application must delete the program item folder and re-create the folder with the Platform flag scalar set correctly.
When a platform flag is set, the network application is available as a program item at computers with the specified platform. When a platform flag is not set for a specific operating system or processor type, the network application is not available to computers with the specified platform—no program item is created and the application is not configured to run on that computer.
When a network application is first configured on a computer, the Program Group Control program can use a setup program or script to configure the registry and initialization files for the application so that it can run over the network.
This entry enables you to specify custom programs or scripts. For example, this line can call a setup program that reads an STF file or a Microsoft Test script. Before distributing the package, you must copy all setup programs and their data files to the package source directory.
If no configuration script or setup program is required, you can set this scalar to NULL.
If you are using a script, type the script processor command (such as MTRUN.EXE or WBRUN20.EXE) followed by the name of the configuration file or script. You can place the script processor in the package source directory.
Note In order for Program Group Control to identify and locate a default script processing program (such as wbrun20.exe, mtrun.exe, and SMSINST.EXE), you must specify the script processor by using .EXE as the part of the command when creating the package (for example, MTRUN.EXE ACCEL.MST).
All other files, including supplied PDFs, must be in the package source directory.
When you set this scalar to TRUE, Program Group Control starts the local version if it finds one; otherwise, it starts the network version. When you set this scalar to FALSE, Program Group Control always runs the network version.
When the Drive mode scalar is set to PI_DRIVEMODE_SPECIFIC_LETTER, Program Group Control must connect using the drive letter specified by the Drive letter scalar. If the specified drive is already used, Program Group Control displays a message box that asks if the user wants to use the next available drive. If the user clicks OK, Program Group Control selects the next available drive and continues the execution of the application. If the user clicks Cancel, Program Group Control terminates without starting the application.
If this entry is left blank, the SMS package identifier number (the site code plus the package number) is used as the registry name. You should specify a recognizable registry name.
Registry names enable an application script to call a dependent application by using its registry name. For example, a Word for Windows script can call an MSAPPS application by using the MSAPPS registry key specified in the program item created for MSAPPS.