Free Trial

Safari Books Online is a digital library providing on-demand subscription access to thousands of learning resources.

Share this Page URL

z/OS UNIX file systems > Running a temporary file system in a colony address sp... - Pg. 439

SYSPRINT For standard output. If SYSPRINT does not exist, LE looks for SYSTERM or SYSERR. If one of those exists, it will be used. But LE does not dynamically allocate either SYSTERM or SYSERR. For standard error. It is also the default message file DD. For capturing dumps formatted by LE. SYSOUT CEEDUMP If any of these names are not currently used in the colony procedure, you must add them with DD DUMMY. If any of the existing DD SYSOUT= statements are not changed, or any of those dynamically allocated by LE are not added, and an attempt is made to open that DD name, the result will be an ABENDS013. Exactly which DD names are opened and when varies by name and product and the situation. There are also other consequences of running outside of JES you may need to consider: SDSF displays will not list the colony address space. There will be no JOBLOG or system messages data set. System messages will go to SYSLOG. SMF recording is different between JES and the master subsystem. 11.2.3 Running a temporary file system in a colony address space In some situations, you may want to run a temporary file system in a colony address space instead of the kernel address space. Because TFS can use up a lot of kernel virtual storage, there may be some environments in which the kernel can run out of private storage. This can happen on large systems with many shell users or in some Lotus environments. By putting the TFS in a colony, impact on the kernel is reduced, and you can have a larger TFS. To cre- ate a cataloged procedure for a temporary file system, the following must be done: 1. Add a FILESYSTYPE statement to your BPXPRMxx member, as follows: FILESYSTYPE TYPE(TFS) ENTRYPOINT(BPXTFS) ASNAME(TFSSTC) 2. Create the cataloged procedure with the name you used for ASNAME in the BPXPRMxx member, and store it in SYS1.PROCLIB, as shown in Figure 11-7. //TFSSTC PROC //******************************************************************** //* z/OS UNIX TFS procedure * //******************************************************************** //TFS EXEC PGM=BPXVCLNY, // REGION=0M, // TIME=1440 //SYSIN DD DUMMY //SYSOUT DD SYSOUT=* //SYSPRINT DD SYSOUT=* //CEEDUMP DD SYSOUT=* // Figure 11-7 Sample of TFS started task 3. Make the entries in the security system for running your cataloged procedure. 4. Activate the definitions in the BPXPRMxx member: a. During the IPL b. Using the SETOMVS RESET=(xx) command, available since OS/390 2.8 5. Mount a TFS file system as shown in Figure 11-8. If you have SYSPLEX(YES) in your system, see Figure 11-9. Chapter 11. Administration 439