You may create a text file of Qshell commands that can be executed as a unit. Such a file is called a script, and is similar in nature to a program written in a language like RPG, CL, or Java, except that scripts are interpreted, not compiled.
The Qshell language is a powerful one, including such features as:
Internal functions (similar to subroutines)
For performance reasons, it is best to place scripts in the root system of the IFS. That is not to say you can't use other file systems. Qshell can run a script stored in a source physical file member, and there's no reason you shouldn't place a script in a source physical file member if doing so fulfills a purpose. But, as a general rule, the root file system is the place to put scripts.
You can use any editor you like as long as you have the appropriate connection to the i5 system. If you want to edit from a terminal session, you can use CL's Edit File (EDTF) command. The EDTF editor is similar to the Source Entry Utility (SEU) in many ways, but not nearly as powerful. EDTF is good for quick changes or small projects, but for ongoing development that includes Qshell, it is better to use a PC workbench.
Figure 27.4 contains a script that creates backup copies of data files.
Figure 27.4: You can develop powerful scripts using Qshell.