DOCSLIB.ORG

CIS Oracle Linux 6 Benchmark

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
CIS Oracle Linux 6 Benchmark CIS Oracle Linux 6 Benchmark v1.0.0 - 06-02-2016 This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International Public License. The link to the license terms can be found at https://creativecommons.org/licenses/by-nc-sa/4.0/legalcode To further clarify the Creative Commons license related to CIS Benchmark content, you are authorized to copy and redistribute the content for use by you, within your organization and outside your organization for non-commercial purposes only, provided that (i) appropriate credit is given to CIS, (ii) a link to the license is provided. Additionally, if you remix, transform or build upon the CIS Benchmark(s), you may only distribute the modified materials if they are subject to the same license terms as the original Benchmark license and your derivative will no longer be a CIS Benchmark. Commercial use of CIS Benchmarks is subject to the prior approval of the Center for Internet Security. 1 | P a g e Table of Contents Overview ............................................................................................................................................................... 12 Intended Audience ........................................................................................................................................ 12 Consensus Guidance ..................................................................................................................................... 12 Typographical Conventions ...................................................................................................................... 13 Scoring Information ..................................................................................................................................... 13 Profile Definitions ......................................................................................................................................... 14 Acknowledgements ...................................................................................................................................... 15 Recommendations ............................................................................................................................................. 16 1 Initial Setup .................................................................................................................................................. 16 1.1 Filesystem Configuration ............................................................................................................... 16 1.1.1.1 Ensure mounting of cramfs filesystems is disabled (Scored) .............................. 17 1.1.1.2 Ensure mounting of freevxfs filesystems is disabled (Scored)............................ 19 1.1.1.3 Ensure mounting of jffs2 filesystems is disabled (Scored) ................................... 20 1.1.1.4 Ensure mounting of hfs filesystems is disabled (Scored) ...................................... 21 1.1.1.5 Ensure mounting of hfsplus filesystems is disabled (Scored) ............................. 22 1.1.1.6 Ensure mounting of squashfs filesystems is disabled (Scored) .......................... 23 1.1.1.7 Ensure mounting of udf filesystems is disabled (Scored) ..................................... 24 1.1.1.8 Ensure mounting of FAT filesystems is disabled (Scored) ................................... 25 1.1.2 Ensure separate partition exists for /tmp (Scored) .................................................... 26 1.1.3 Ensure nodev option set on /tmp partition (Scored) ................................................. 28 1.1.4 Ensure nosuid option set on /tmp partition (Scored) ................................................ 29 1.1.5 Ensure noexec option set on /tmp partition (Scored) ............................................... 30 1.1.6 Ensure separate partition exists for /var (Scored) ..................................................... 31 1.1.7 Ensure separate partition exists for /var/tmp (Scored) ........................................... 32 1.1.8 Ensure nodev option set on /var/tmp partition (Scored) ........................................ 33 1.1.9 Ensure nosuid option set on /var/tmp partition (Scored) ....................................... 34 1.1.10 Ensure noexec option set on /var/tmp partition (Scored) .................................... 35 2 | P a g e 1.1.11 Ensure separate partition exists for /var/log (Scored) .......................................... 36 1.1.12 Ensure separate partition exists for /var/log/audit (Scored) ............................. 37 1.1.13 Ensure separate partition exists for /home (Scored) .............................................. 38 1.1.14 Ensure nodev option set on /home partition (Scored) ........................................... 39 1.1.15 Ensure nodev option set on /dev/shm partition (Scored) .................................... 40 1.1.16 Ensure nosuid option set on /dev/shm partition (Scored) ................................... 41 1.1.17 Ensure noexec option set on /dev/shm partition (Scored) .................................. 42 1.1.18 Ensure nodev option set on removable media partitions (Not Scored) ........... 43 1.1.19 Ensure nosuid option set on removable media partitions (Not Scored) .......... 44 1.1.20 Ensure noexec option set on removable media partitions (Not Scored) ......... 45 1.1.21 Ensure sticky bit is set on all world-writable directories (Scored) .................... 46 1.1.22 Disable Automounting (Scored) ....................................................................................... 47 1.2 Configure Software Updates ......................................................................................................... 49 1.2.1 Ensure package manager repositories are configured (Not Scored) ................... 49 1.2.2 Ensure GPG keys are configured (Not Scored) .............................................................. 50 1.2.3 Ensure gpgcheck is globally activated (Scored) ........................................................... 51 1.3 Filesystem Integrity Checking ...................................................................................................... 52 1.3.1 Ensure AIDE is installed (Scored) ...................................................................................... 52 1.3.2 Ensure filesystem integrity is regularly checked (Scored) ....................................... 54 1.4 Secure Boot Settings ........................................................................................................................ 55 1.4.1 Ensure permissions on bootloader config are configured (Scored) ..................... 55 1.4.2 Ensure bootloader password is set (Scored) ................................................................. 56 1.4.3 Ensure authentication required for single user mode (Scored) ............................. 57 1.4.4 Ensure interactive boot is not enabled (Scored) .......................................................... 58 1.5 Additional Process Hardening ..................................................................................................... 59 1.5.1 Ensure core dumps are restricted (Scored) ................................................................... 59 1.5.2 Ensure XD/NX support is enabled (Not Scored) .......................................................... 61 1.5.3 Ensure address space layout randomization (ASLR) is enabled (Scored) ......... 63 1.5.4 Ensure prelink is disabled (Scored) .................................................................................. 64 1.6 Mandatory Access Control ............................................................................................................. 64 3 | P a g e 1.6.1.1 Ensure SELinux is not disabled in bootloader configuration (Scored) ............ 67 1.6.1.2 Ensure the SELinux state is enforcing (Scored) ........................................................ 68 1.6.1.3 Ensure SELinux policy is configured (Scored) ........................................................... 69 1.6.1.4 Ensure SETroubleshoot is not installed (Scored) ..................................................... 70 1.6.1.5 Ensure the MCS Translation Service (mcstrans) is not installed (Scored) ..... 71 1.6.1.6 Ensure no unconfined daemons exist (Scored) ......................................................... 72 1.6.2 Ensure SELinux is installed (Scored) ................................................................................ 73 1.7 Warning Banners............................................................................................................................... 73 1.7.1.1 Ensure message of the day is configured properly (Scored) ............................... 75 1.7.1.2 Ensure local login warning banner is configured properly (Not Scored) ....... 77 1.7.1.3 Ensure remote login warning banner is configured properly (Not Scored) .. 79 1.7.1.4 Ensure permissions on /etc/motd are configured (Not Scored) ....................... 81 1.7.1.5 Ensure permissions on /etc/issue are configured (Scored) ................................ 82 1.7.1.6 Ensure permissions on /etc/issue.net are configured (Not Scored) ................ 83 1.7.2 Ensure GDM login banner is configured (Scored) ........................................................ 84 1.8 Ensure updates, patches, and additional security software are installed (Not Scored) ..................................................................................................................................................... 86
Load more

Recommended publications
  • Administering Unidata on UNIX Platforms
    C:\Program Files\Adobe\FrameMaker8\UniData 7.2\7.2rebranded\ADMINUNIX\ADMINUNIXTITLE.fm March 5, 2010 1:34 pm Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta UniData Administering UniData on UNIX Platforms UDT-720-ADMU-1 C:\Program Files\Adobe\FrameMaker8\UniData 7.2\7.2rebranded\ADMINUNIX\ADMINUNIXTITLE.fm March 5, 2010 1:34 pm Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Notices Edition Publication date: July, 2008 Book number: UDT-720-ADMU-1 Product version: UniData 7.2 Copyright © Rocket Software, Inc. 1988-2010. All Rights Reserved. Trademarks The following trademarks appear in this publication: Trademark Trademark Owner Rocket Software™ Rocket Software, Inc. Dynamic Connect® Rocket Software, Inc. RedBack® Rocket Software, Inc. SystemBuilder™ Rocket Software, Inc. UniData® Rocket Software, Inc. UniVerse™ Rocket Software, Inc. U2™ Rocket Software, Inc. U2.NET™ Rocket Software, Inc. U2 Web Development Environment™ Rocket Software, Inc. wIntegrate® Rocket Software, Inc. Microsoft® .NET Microsoft Corporation Microsoft® Office Excel®, Outlook®, Word Microsoft Corporation Windows® Microsoft Corporation Windows® 7 Microsoft Corporation Windows Vista® Microsoft Corporation Java™ and all Java-based trademarks and logos Sun Microsystems, Inc. UNIX® X/Open Company Limited ii SB/XA Getting Started The above trademarks are property of the specified companies in the United States, other countries, or both. All other products or services mentioned in this document may be covered by the trademarks, service marks, or product names as designated by the companies who own or market them. License agreement This software and the associated documentation are proprietary and confidential to Rocket Software, Inc., are furnished under license, and may be used and copied only in accordance with the terms of such license and with the inclusion of the copyright notice.
    [Show full text]
  • Membrane: Operating System Support for Restartable File Systems Swaminathan Sundararaman, Sriram Subramanian, Abhishek Rajimwale, Andrea C
    Membrane: Operating System Support for Restartable File Systems Swaminathan Sundararaman, Sriram Subramanian, Abhishek Rajimwale, Andrea C. Arpaci-Dusseau, Remzi H. Arpaci-Dusseau, Michael M. Swift Computer Sciences Department, University of Wisconsin, Madison Abstract and most complex code bases in the kernel. Further, We introduce Membrane, a set of changes to the oper- file systems are still under active development, and new ating system to support restartable file systems. Mem- ones are introduced quite frequently. For example, Linux brane allows an operating system to tolerate a broad has many established file systems, including ext2 [34], class of file system failures and does so while remain- ext3 [35], reiserfs [27], and still there is great interest in ing transparent to running applications; upon failure, the next-generation file systems such as Linux ext4 and btrfs. file system restarts, its state is restored, and pending ap- Thus, file systems are large, complex, and under develop- plication requests are serviced as if no failure had oc- ment, the perfect storm for numerous bugs to arise. curred. Membrane provides transparent recovery through Because of the likely presence of flaws in their imple- a lightweight logging and checkpoint infrastructure, and mentation, it is critical to consider how to recover from includes novel techniques to improve performance and file system crashes as well. Unfortunately, we cannot di- correctness of its fault-anticipation and recovery machin- rectly apply previous work from the device-driver litera- ery. We tested Membrane with ext2, ext3, and VFAT. ture to improving file-system fault recovery. File systems, Through experimentation, we show that Membrane in- unlike device drivers, are extremely stateful, as they man- duces little performance overhead and can tolerate a wide age vast amounts of both in-memory and persistent data; range of file system crashes.
    [Show full text]
  • Ext4 File System and Crash Consistency
    1 Ext4 file system and crash consistency Changwoo Min 2 Summary of last lectures • Tools: building, exploring, and debugging Linux kernel • Core kernel infrastructure • Process management & scheduling • Interrupt & interrupt handler • Kernel synchronization • Memory management • Virtual file system • Page cache and page fault 3 Today: ext4 file system and crash consistency • File system in Linux kernel • Design considerations of a file system • History of file system • On-disk structure of Ext4 • File operations • Crash consistency 4 File system in Linux kernel User space application (ex: cp) User-space Syscalls: open, read, write, etc. Kernel-space VFS: Virtual File System Filesystems ext4 FAT32 JFFS2 Block layer Hardware Embedded Hard disk USB drive flash 5 What is a file system fundamentally? int main(int argc, char *argv[]) { int fd; char buffer[4096]; struct stat_buf; DIR *dir; struct dirent *entry; /* 1. Path name -> inode mapping */ fd = open("/home/lkp/hello.c" , O_RDONLY); /* 2. File offset -> disk block address mapping */ pread(fd, buffer, sizeof(buffer), 0); /* 3. File meta data operation */ fstat(fd, &stat_buf); printf("file size = %d\n", stat_buf.st_size); /* 4. Directory operation */ dir = opendir("/home"); entry = readdir(dir); printf("dir = %s\n", entry->d_name); return 0; } 6 Why do we care EXT4 file system? • Most widely-deployed file system • Default file system of major Linux distributions • File system used in Google data center • Default file system of Android kernel • Follows the traditional file system design 7 History of file system design 8 UFS (Unix File System) • The original UNIX file system • Design by Dennis Ritche and Ken Thompson (1974) • The first Linux file system (ext) and Minix FS has a similar layout 9 UFS (Unix File System) • Performance problem of UFS (and the first Linux file system) • Especially, long seek time between an inode and data block 10 FFS (Fast File System) • The file system of BSD UNIX • Designed by Marshall Kirk McKusick, et al.
    [Show full text]
  • Open Source Licensing Information for Cisco IP Phone 8800 Series
    Open Source Used In Cisco IP Phone 8800 Series 12.1(1) Cisco Systems, Inc. www.cisco.com Cisco has more than 200 offices worldwide. Addresses, phone numbers, and fax numbers are listed on the Cisco website at www.cisco.com/go/offices. Text Part Number: 78EE117C99-163803748 Open Source Used In Cisco IP Phone 8800 Series 12.1(1) 1 This document contains licenses and notices for open source software used in this product. With respect to the free/open source software listed in this document, if you have any questions or wish to receive a copy of any source code to which you may be entitled under the applicable free/open source license(s) (such as the GNU Lesser/General Public License), please contact us at [email protected]. In your requests please include the following reference number 78EE117C99-163803748 Contents 1.1 bluez 4.101 :MxC-1.1C R4.0 1.1.1 Available under license 1.2 BOOST C++ Library 1.63.0 1.2.1 Available under license 1.3 busybox 1.21.0 1.3.1 Available under license 1.4 Busybox 1.23.1 1.4.1 Available under license 1.5 cjose 0.4.1 1.5.1 Available under license 1.6 cppformat 2.0.0 1.6.1 Available under license 1.7 curl 7.26.0 1.7.1 Available under license 1.8 dbus 1.4.1 :MxC-1.1C R4.0 1.8.1 Available under license 1.9 DirectFB library and utilities 1.4.5 1.9.1 Available under license 1.10 dnsmasq 2.46 1.10.1 Available under license 1.11 flite 2.0.0 1.11.1 Available under license 1.12 glibc 2.13 1.12.1 Available under license 1.13 hostapd 2.0 :MxC-1.1C R4.0 1.13.1 Available under license Open Source Used
    [Show full text]
  • De-Anonymizing Live Cds Through Physical Memory Analysis
    De-Anonymizing Live CDs through Physical Memory Analysis Andrew Case [email protected] Digital Forensics Solutions Abstract Traditional digital forensics encompasses the examination of data from an offline or “dead” source such as a disk image. Since the filesystem is intact on these images, a number of forensics techniques are available for analysis such as file and metadata examination, timelining, deleted file recovery, indexing, and searching. Live CDs present a serious problem for this investigative model, however, since the OS and applications execute in a RAM-only environment and do not save data on non-volatile storage devices such as the local disk. In order to solve this problem, we present a number of techniques that support complete recovery of a live CD’s in-memory filesystem and partial recovery of its deleted contents. We also present memory analysis of the popular Tor application, since it is used by a number of live CDs in an attempt to keep network communications encrypted and anonymous. 1 Introduction Traditional digital forensics encompasses the examination of data from an offline or “dead” source such as a disk image. Under normal circumstances, evidence is obtained by first creating an exact, bit-for-bit copy of the target disk, followed by hashing of both the target disk and the new copy. If these hashes match then it is known that an exact copy has been made, and the hash is recorded to later prove that evidence was not modified during the investigation. Besides satisfying legal requirements, obtaining a bit-for-bit copy of data provides investigators with a wealth of information to examine and makes available a number of forensics techniques.
    [Show full text]
  • EZ-SCREEN LP Instruction Manual
    EZ-SCREEN® LP Low-Profile Safety Light Screen Instruction Manual Original Instructions 140044 Rev. G 27 April 2018 © Banner Engineering Corp. All rights reserved 140044 EZ-SCREEN® LP Low-Profile Safety Light Screen Contents 1 About This Document .............................................................................................................................................5 1.1 Important . Read This Before Proceeding! .....................................................................................................................5 1.2 Use of Warnings and Cautions ...........................................................................................................................................5 1.3 EU Declaration of Conformity (DoC) ..................................................................................................................................5 1.4 Banner Engineering Corp Limited Warranty ......................................................................................................................6 1.5 Contact Us ......................................................................................................................................................................... 6 2 Introduction ............................................................................................................................................................ 8 2.1 Features .............................................................................................................................................................................8
    [Show full text]
  • Banner 8 Student System
    BANNER STUDENT Viewing Student Information Department: Student Information Management Email:[email protected] Phone: 646-7383 Last Update: March 1, 2010 Banner Student Confidential Business Information This documentation is proprietary information of New Mexico State University (NMSU) and is not to be copied, reproduced, lent or disposed of, nor used for any purpose other than that for which it is specifically provided without the written permission of NMSU. Prepared For: Release 8.x Prepared By: New Mexico State University P.O. Box 30001 Las Cruces, New Mexico 88003 United States of America Issued: October 2012 In preparing and providing this publication, NMSU is not rendering legal, accounting, or other similar professional services. NMSU makes no claims that an institution’s use of this publication or the software for which it is provided will insure compliance with applicable federal or state laws, rules, or regulations. Each organization should seek legal, accounting and other similar professional services from competent providers of the organization’s own choosing. © 2010 Regents of New Mexico State University. SunGard or its subsidiaries in the U.S. and other countries is the owner of numerous marks, including “SunGard,” the SunGard logo, “Banner,” “PowerCAMPUS,” “Advance,” “Luminis”, "fsaATLAS," "DegreeWorks," "SEVIS Connection," "SmartCall," “UDC,” and “Unified Digital Campus.” Other names and marks used in this material are owned by third parties. Use of this material is solely for the support of SunGard HE Banner products and NMSU. © SunGard 2006. All rights reserved. The unauthorized possession, use, reproduction, distribution, display or disclosure of this material or the information contained herein is prohibited.
    [Show full text]
  • POSIX Freeware
    2115 POSIX Freeware Michael D. Hensley Allegro Consultants, Inc. 2101 Woodside Road Redwood City, CA 94062 (415) 369-2303 voice (415) 369-2304 fax [email protected] http://www.allegro.com Before you can really begin to explore and use the POSIX freeware, it would help to familiarize yourself with POSIX. What Is POSIX? To keep things simple, POSIX is a set of standards based on UNIX. There are three major areas covered by the standards: an end-user shell, a set of utilities, and a collection of programming functions. This paper will get you started with the shell and utilities. When I talk about "POSIX", I'll generally be referring only to the shell and utilities. What Is A POSIX File? The POSIX standards require a "hierarchical file system", like the on UNIX and MSDOS/WINDOWS PC's. HP added a hierarchical file system (usually referred to as the HFS) to MPE with version 4.5. If you have never used UNIX or a PC (or even if you have), you can learn more about the HFS by logging on to your MPE system and typing :XEQ POSIXCBT.LSN.SYS This runs an on-line tutorial about the HFS. POSIX also requires that filenames be case-sensitive (i.e. "FOOBAR" and "FooBar" are two different files). These two things (the HFS and the case-sensitive filenames) create much of the confusion about "POSIX files", but here's the secret: There really isn't any such thing as a "POSIX file" or a "non- POSIX file"! A file is a file is a file.
    [Show full text]
  • Hardware-Driven Evolution in Storage Software by Zev Weiss A
    Hardware-Driven Evolution in Storage Software by Zev Weiss A dissertation submitted in partial fulfillment of the requirements for the degree of Doctor of Philosophy (Computer Sciences) at the UNIVERSITY OF WISCONSIN–MADISON 2018 Date of final oral examination: June 8, 2018 ii The dissertation is approved by the following members of the Final Oral Committee: Andrea C. Arpaci-Dusseau, Professor, Computer Sciences Remzi H. Arpaci-Dusseau, Professor, Computer Sciences Michael M. Swift, Professor, Computer Sciences Karthikeyan Sankaralingam, Professor, Computer Sciences Johannes Wallmann, Associate Professor, Mead Witter School of Music i © Copyright by Zev Weiss 2018 All Rights Reserved ii To my parents, for their endless support, and my cousin Charlie, one of the kindest people I’ve ever known. iii Acknowledgments I have taken what might be politely called a “scenic route” of sorts through grad school. While Ph.D. students more focused on a rapid graduation turnaround time might find this regrettable, I am glad to have done so, in part because it has afforded me the opportunities to meet and work with so many excellent people along the way. I owe debts of gratitude to a large cast of characters: To my advisors, Andrea and Remzi Arpaci-Dusseau. It is one of the most common pieces of wisdom imparted on incoming grad students that one’s relationship with one’s advisor (or advisors) is perhaps the single most important factor in whether these years of your life will be pleasant or unpleasant, and I feel exceptionally fortunate to have ended up iv with the advisors that I’ve had.
    [Show full text]
  • Elinos Product Overview
    SYSGO Product Overview ELinOS 7 Industrial Grade Linux ELinOS is a SYSGO Linux distribution to help developers save time and effort by focusing on their application. Our Industrial Grade Linux with user-friendly IDE goes along with the best selection of software packages to meet our cog linux Qt LOCK customers needs, and with the comfort of world-class technical support. ELinOS now includes Docker support Feature LTS Qt Open SSH Configurator Kernel embedded Open VPN in order to isolate applications running on the same system. laptop Q Bug Shield-Virus Docker Eclipse-based QEMU-based Application Integrated Docker IDE HW Emulators Debugging Firewall Support ELINOS FEATURES MANAGING EMBEDDED LINUX VERSATILITY • Industrial Grade Creating an Embedded Linux based system is like solving a puzzle and putting • Eclipse-based IDE for embedded the right pieces together. This requires a deep knowledge of Linux’s versatility Systems (CODEO) and takes time for the selection of components, development of Board Support • Multiple Linux kernel versions Packages and drivers, and testing of the whole system – not only for newcomers. incl. Kernel 4.19 LTS with real-time enhancements With ELinOS, SYSGO offers an ‘out-of-the-box’ experience which allows to focus • Quick and easy target on the development of competitive applications itself. ELinOS incorporates the system configuration appropriate tools, such as a feature configurator to help you build the system and • Hardware Emulation (QEMU) boost your project success, including a graphical configuration front-end with a • Extensive file system support built-in integrity validation. • Application debugging • Target analysis APPLICATION & CONFIGURATION ENVIRONMENT • Runs out-of-the-box on PikeOS • Validated and tested for In addition to standard tools, remote debugging, target system monitoring and PowerPC, x86, ARM timing behaviour analyses are essential for application development.
    [Show full text]
  • AMD Alchemy™ Processors Building a Root File System for Linux® Incorporating Memory Technology Devices
    AMD Alchemy™ Processors Building a Root File System for Linux® Incorporating Memory Technology Devices 1.0 Scope This document outlines a step-by-step process for building and deploying a Flash-based root file system for Linux® on an AMD Alchemy™ processor-based development board, using an approach that incorporates Memory Technology Devices (MTDs) with the JFFS2 file system. Note: This document describes creating a root file system on NOR Flash memory devices, and does not apply to NAND Flash devices. 1.1 Journaling Flash File System JFFS2 is the second generation of the Journaling Flash File System (JFFS). This file system provides a crash-safe and powerdown-safe Linux file system for use with Flash memory devices. The home page for the JFFS project is located at http://developer.axis.com/software/jffs. 1.2 Memory Technology Device The MTD subsystem provides a generic Linux driver for a wide range of memory devices, including Flash memory devices. This driver creates an abstracted device used by JFFS2 to interface to the actual Flash memory hardware. The home page for the MTD project is located at http://www.linux-mtd.infradead.org. 2.0 Building the Root File System Before being deployed to an AMD Alchemy platform, the file system must first be built on an x86 Linux host PC. The pri- mary concern when building a Flash-based root file system is often the size of the image. The file system must be designed so that it fits within the available space of the Flash memory, with enough extra space to accommodate any runtime-created files, such as temporary or log files.
    [Show full text]
  • Banner Running Jobs (Reports) in Banner
    Banner Running Jobs (Reports) in Banner A Banner “job” is a report or process. Processes make global modifications to the database, but typically produce little valuable printed results. Examples include fee assessment, GPA calculation, letter extraction, and posting to the ledger. Reports are run primarily for the printed results. Examples include transcripts, bills, letters and budget reports. Since the client (PC) is actually running the “Job Submission” form (GJAPCTL), and the report is actually running on the Unix (Sun) computer, jobs will not prompt for parameters at runtime. All parameters must be specified in the parameter block of GJAPCTL. After submitting the job, you will immediately go back to Banner (while the job is running on the Sun computer). Output from the report or process will remain on the Sun computer. After the job is done running, you may connect to the Sun computer to spool the file. Running (Submitting) a Job To run a job (report or process), enter the job name using “Direct Access”, or select the Process Submission Control Form (GJAPCTL) from Direct Access or a menu: In the “Process” field, enter the name of the report or process you wish to run. You may issue aListFieldValuesfunction or click on the Processbutton to list all jobs that you have permission to run. If you have saved a parameter set for this report that you wish to use again, use NextField to move to the “Parameter Set” field and enter the parameter set name (or use ListFieldValuesto list sets you have already stored). Issue the NextBlock function to move to the "Printer Control” block.
    [Show full text]