Sidebar

Getting Into Outfiles

CL
Typography
  • Smaller Small Medium Big Bigger
  • Default Helvetica Segoe Georgia Times

Steps to analyze the outfile format.

1. Run the command (refer to Figures 1 and 2 for options).

2. Use DSPFFD to view the file structure.

3. Look at the outfile data with CPYF or Query.

4. Run the command with output to the workstation.

Use the outfile as an externally defined file.

Using an outfile requires a thorough investigation.

Brief: Many system-supplied and QUSRTOOL commands have an OUTFILE parameter that can be used to direct system information to a database file. Although outfiles are not difficult to use, you must know which commands provide this capability and how to interpret the file. Once you have the outfile, you can use it in your programs like any other database file.

If you have not already written or worked with AS/400 commands that use outfiles, chances are that you will at some point. A casual review of recent issues of Midrange Computing magazine shows several instances where outfiles are used in utility and sample programs, so it is not difficult to locate examples. A more difficult task, however, is grasping the concepts and basics of outfiles, which are seldom discussed.

Outfiles constitute one of the methods you can use to get your system to tell you about itself. They are an option in addition to displays and printed listings of system-maintained information. Typically, you can use outfiles to get lists of objects in a library, members or fields in a file, hardware and software resources, authorities, distributions and other configuration data. Unfortunately, you cannot assume that all system information commands (the WRK and DSP commands) supply an outfile option; in fact, many of them do not.

The basic idea of an outfile (which is a shortened form of output file) is that certain system commands can be directed to write their output to a predefined database file, rather than to your display or to a printed listing. You can use that database file in your programs, exactly as you would a file that you create.

There are really only two issues that you need to be aware of when creating a program that uses an outfile. First, is there an outfile available for the information that you need? Second, if there is such an outfile, what is the format of the information?

Commands That Supply Outfiles

A list of system-supplied commands that provide an OUTFILE parameter is shown in 1. (The chart is adapted from the Database Guide, SC41-9659, CD book QPRG1DAT.) Also shown in the figure are the names of the system-supplied model outfiles and the record formats in the outfiles.

A list of system-supplied commands that provide an OUTFILE parameter is shown in Figure 1. (The chart is adapted from the Database Guide, SC41-9659, CD book QPRG1DAT.) Also shown in the figure are the names of the system-supplied model outfiles and the record formats in the outfiles.

The first step in using an outfile is either to review the chart to determine if there is a command that supplies the type of information you need in an outfile, or to prompt for the command and see if there is an OUTFILE parameter. In addition to the system-supplied commands that provide an outfile, there are 20 commands in the QUSRTOOL library that convert system information into outfiles. Those commands, the CVT commands, are listed in 2.

The first step in using an outfile is either to review the chart to determine if there is a command that supplies the type of information you need in an outfile, or to prompt for the command and see if there is an OUTFILE parameter. In addition to the system-supplied commands that provide an outfile, there are 20 commands in the QUSRTOOL library that convert system information into outfiles. Those commands, the CVT commands, are listed in Figure 2.

If a system or QUSRTOOL command does not write the information you want to an outfile, you are faced with the unpleasant prospect of writing a program that retrieves the printed information and writes it to an outfile. For example, the Display Override (DSPOVR) command does not provide an OUTFILE parameter, even though you might want to have the output directed to a database file from that command. The usual practice with a command like DSPOVR is to run it with output to a printed listing, then use the Copy Spooled File (CPYSPLF) command to copy the spool file to a database file. You then run a special customized program to read the CPYSPLF file, picking out the fields you need and writing them to a database file that is used as your outfile. That's your course of action if you want to create your own command with outfile capability, and it's the approach that most of the QUSRTOOL CVT commands use. Alter-natively, if you do not need to create a general purpose command, you can simply code the spool file analysis in the program and process the CPYSPLF file directly. If you use one of these methods, be aware that you'll need to check your program or command with each new release of OS/400, since the format of the printed listing could change.

Files That Are Supplied

For the commands shown in1 and 2, the system-supplied outfiles and record formats are shown. You can determine the name of these outfiles as well as the record format for some of the commands by using the Help key on the OUTFILE parameter when the command prompter is used. Most of the commands provide only one outfile format, although there are a few (such as Display File Description [DSPFD], Display Hardware Resources [DSPHDWRSC] and Display Journal [DSPJRN]) that work with more than one format. The outfiles listed in 1 are located in library QSYS. These files don't contain data-they are used for definition only. Like most other IBM-supplied objects, you should not change, delete or move them.

For the commands shown in Figures 1 and 2, the system-supplied outfiles and record formats are shown. You can determine the name of these outfiles as well as the record format for some of the commands by using the Help key on the OUTFILE parameter when the command prompter is used. Most of the commands provide only one outfile format, although there are a few (such as Display File Description [DSPFD], Display Hardware Resources [DSPHDWRSC] and Display Journal [DSPJRN]) that work with more than one format. The outfiles listed in Figure 1 are located in library QSYS. These files don't contain data-they are used for definition only. Like most other IBM-supplied objects, you should not change, delete or move them.

You will find that there are no DDS source members provided for the system- supplied outfiles. The DDS source members are included for the QUSRTOOL commands (in source file QUSRTOOL/QATTDDS), although you will have to do some research to match up the DDS source member with the corresponding outfile for a QUSRTOOL command. 2 lists the QUSRTOOL outfiles with the names that are used when the commands are executed.

You will find that there are no DDS source members provided for the system- supplied outfiles. The DDS source members are included for the QUSRTOOL commands (in source file QUSRTOOL/QATTDDS), although you will have to do some research to match up the DDS source member with the corresponding outfile for a QUSRTOOL command. Figure 2 lists the QUSRTOOL outfiles with the names that are used when the commands are executed.

Although the DDS is not supplied, if you know the name of the outfile for a system-supplied command you can determine what information is available. You accomplish that by running the Display File Field Description (DSPFFD) command for the outfile. This command displays or prints a list of fields in the file. You can review the list to see the field names, types, lengths and descriptions-the same field level information you would get from a DDS source member. 3 presents a sample listing from DSPFFD. For a QUSRTOOL command, you should first run the command (to generate the outfile) and then run the DSPFFD command for the outfile.

Although the DDS is not supplied, if you know the name of the outfile for a system-supplied command you can determine what information is available. You accomplish that by running the Display File Field Description (DSPFFD) command for the outfile. This command displays or prints a list of fields in the file. You can review the list to see the field names, types, lengths and descriptions-the same field level information you would get from a DDS source member. Figure 3 presents a sample listing from DSPFFD. For a QUSRTOOL command, you should first run the command (to generate the outfile) and then run the DSPFFD command for the outfile.

Specifying a File to Use as an Outfile

When you run a command that supports an outfile, you name the outfile and indicate the library in which you want the file to be located. The name you use can be the same as the system-supplied name or any other name that you want. You can choose any library for the outfile; however, you cannot specify library QSYS if you use the system-supplied outfile name. If you do, escape message CPF3072 is sent, indicating that the file is a system file.

All of the system-supplied commands with outfile support (with the exception of the RUNQRY command), and most of the QUSRTOOL commands, include an output member (OUTMBR) parameter. For the system-supplied commands, this parameter names the member in the outfile that is to contain the records. A second part of the OUTMBR parameter is used to stipulate whether to add records to existing records in the member or replace existing records. The default for the member name is *FIRST and the default for the add/replace option is *REPLACE. (The QUSRTOOL commands use separate OUTMBR and REPLACE parameters for these options, rather than combining them into the one OUTMBR parameter.)

When you run a command to an outfile, you can use a new or existing file. If you choose an existing file, you must ensure that the format of the existing file is the same as the format of the model file. For example, you cannot direct the output from a Display File Description (DSPFD) command to an outfile created by the Display Directory (DSPDIR) command. If the outfile name that you selected does not exist, a copy of the outfile is created from the model outfile used by the command. If you do not designate a member name, a member is added to the file with the same name as the file.

When you run an outfile-capable command several times, using the same file name, the values specified for the OUTMBR parameter control how the data is written. If you assign a member name that does not exist in the outfile, the member is added and records are written to that member. For an existing member, the add/replace option is used.

Determining What's in an Outfile

As mentioned, the primary method used to determine what information is in an outfile is to use the system-supplied DSPFFD command. The majority of the fields available in any outfile are self-explanatory, but there are instances where the fields or the values that are put into those fields are unclear. Unfortunately, I have found minimal documentation on outfile fields, other than the 50-character text description associated with the field.

I have discovered that the best way to understand what is in an outfile is to actually run the command to create the outfile, run the DSPFFD command to list the fields in the outfile, and then dump some of the outfile records, either with the CPYF command or with a simple query. Since I am usually only interested in a few of the fields, I try to identify those and ignore the rest. You can sometimes spot those fields more quickly with the file dump rather than the DSPFFD listing. If I get really stuck or am unclear about the values in a field, I run the command with output to my terminal and review the fields on the display.

For the commands that provide multiple outfiles, such as the DSPFD command, you may want to run the command first with the display or print option. Once you determine which combination of command parameters provides you with the required information, you can run the command with the outfile option.

Using Outfiles in Your Programs

After running a command that creates an outfile, you can use the file like any other database file. You can copy from and to it, run queries against it, sort it or build logical files over it, or use it in a CL or other HLL program.

Outfiles are externally defined files in your programs and, like any other externally defined file, the outfile must exist before compiling the program. If you are using a system-supplied outfile, you can simply specify the name of the model outfile on your program's file definition statement (the RPG F- spec); the file definition is found in library QSYS. Unlike the system- supplied outfiles, the QUSRTOOL outfiles do not exist until the command that uses them is run. For a QUSRTOOL outfile, you will have to run the command first to create a version of the outfile, using the same name for the outfile as the name used in your program.

Because outfiles are usually temporary files that are needed only for the duration of the program that uses them, you will typically designate QTEMP as the library to contain the outfile. You must be sure that when your program runs it is able to locate the outfile you just created. The safest technique is to use the OVRDBF command to direct your program to open the outfile in the library where the command created it. As an alternative to creating the outfile in QTEMP or another library, you can set up the outfiles that you use as "permanent" work files. (See "TechTalk" in the February 1992 issue of Midrange Computing for a discussion of using permanent work files.)

Keyed Access to an Outfile

If you want to use an outfile with a keyed access path, you can employ a technique that does not involve creating a logical file over the outfile. The file is created as a physical file with the DDS FORMAT keyword because the file is sharing the format of the system-supplied outfile. The record format name is the same as the format name in the system-supplied file. This is similar to using the CRTDUPOBJ command to create a duplicate of the file. However, because we are duplicating the file in DDS, we can also add to the definition of the duplicate file, specifically by adding key fields to indicate the required access path.

To use this technique, you first create the DDS specifications for the outfile that you are going to use, similar to the sample shown in 4. Then you run the Create Physical File (CRTPF) command from those specifications. Once the file is created, you can name it on the OUTFILE parameter of the appropriate command. Because it is an existing file with the same record format, the command can write the records to the file. Your programs can then use the file as a keyed file. However, you cannot define select/omit fields, because you are creating a physical file. If you need that capability, you'll have to define a logical file over the outfile that you create.

To use this technique, you first create the DDS specifications for the outfile that you are going to use, similar to the sample shown in Figure 4. Then you run the Create Physical File (CRTPF) command from those specifications. Once the file is created, you can name it on the OUTFILE parameter of the appropriate command. Because it is an existing file with the same record format, the command can write the records to the file. Your programs can then use the file as a keyed file. However, you cannot define select/omit fields, because you are creating a physical file. If you need that capability, you'll have to define a logical file over the outfile that you create.

The sidebar on page 70 illustrates how you can use an outfile in a CL program and gives you a solution to one of the pitfalls of this technique. As additional examples, I want to refer you to several recent articles in Midrange Computing that use outfile processing. Those articles are listed in 5. The listing is fairly representative of the frequency with which outfiles are used. As you can tell from the article titles, most of the usage falls into the utility program arena.

The sidebar on page 70 illustrates how you can use an outfile in a CL program and gives you a solution to one of the pitfalls of this technique. As additional examples, I want to refer you to several recent articles in Midrange Computing that use outfile processing. Those articles are listed in Figure 5. The listing is fairly representative of the frequency with which outfiles are used. As you can tell from the article titles, most of the usage falls into the utility program arena.

If you are unfamiliar with using files in CL programs, you should pay particular attention to the "Files in CL" article. That example provides a shell program that you can use to process a file in a CL program. Many of the examples of using outfiles are of the outfile being used in a CL program, although there is no reason why the outfile cannot be used in any other type of program.

Investigation Pays Off

Outfiles are really no different from any other type of database file that you can create and use. The main considerations for using outfiles are determining what is available and the meaning of the information, which involves some research and experimentation on your part. However, once you have tried a few examples, you will find a pattern that you can use to locate, examine and use an outfile.

Examples of Using Outfiles

One of the problems you may encounter is processing an outfile in the same CL program that creates it. To process the file, the CL program needs the Declare File (DCLF) command, which assumes that the file already exists. But the file may not exist since the command that creates the outfile hasn't been executed yet (the command will be executed in the program). It's a Catch-22 situation, but there's a way out.

Remember that the model files for system-supplied outfiles exist in QSYS. To solve the problem, use these four steps:

1. Code your DCLF command using the system-supplied file name in QSYS, but without actually referencing QSYS. Don't use any library qualifier. When you compile the program, the compiler will find the file in QSYS.

2. Code the command that produces the outfile, choosing in the OUTFILE parameter the same name as the model file, but qualified with QTEMP or any other library (except QSYS). QTEMP is recommended, however, because in that case the file is automatically deleted when the job ends.

3. Code an Override with Database File (OVRDBF) command, naming the model file in the FILE parameter and the actual file you produced (in QTEMP or elsewhere) in the TOFILE parameter.

4. Process the file with the Receive File (RCVF) command which will read the copy in QTEMP because of the previous OVRDBF.

The skeleton program depicted in the figure below illustrates the process. If you adopt this approach, you can compile the program without trouble, since the file declared in DCLF exists in QSYS.

Skeleton CL Program Using an Outfile

 PROGRAM: PGM DCLF FILE(QADSPOBJ) DSPOBJD OBJ(*ALL) OBJTYPE(*DEVD) OUTPUT(*OUTFILE) + OUTFILE(QTEMP/QADSPOBJ) OVRDBF FILE(QADSPOBJ) TOFILE(QTEMP/QADSPOBJ) LOOP: RCVF MONMSG MSGID(CPF0864) EXEC(GOTO CMDLBL(END_LOOP)) /* Include commands to process the record */ GOTO CMDLBL(LOOP) END_LOOP: /* Etc. */ ENDPGM 

References:

Database Guide, SC41-9658 (CD book QPRG1DAT)

Programming: Reference Summary, SX41-0028 (CD book QSYSSUM)

System Programmer's Interface Reference, SC41-8223 (CD book QPRG2SPI)


Getting Into Outfiles

Figure 1 Command that support OUTFILE parameter

 Figure 1: Commands That Support OUTFILE Parameter Model Format Command File Name Notes DSPAUTHLR QADSHLR QSYDSHLR DSPAUTL QAOBJAUT QSYDSAUT DSPAUTLOBJ QADALO QSYDALO DSPDBR QADSPDBR QWHDRDBR DSPDIR QAOSDIRO OSDIRE OUTFILFMT(*TYPE1) QAOSDIRB OSDIRB OUTFILFMT(*TYPE2) DETAIL(*BASIC) QAOSDIRF OSDIRF OUTFILFMT(*TYPE2) DETAIL(*FULL) QAOSDIRX OSDIRX OUTFILFMT(*TYPE3) DETAIL(*FULL) DSPDSTL QAOSDSTO OSDSTL DSPFD QAFDACCP QWHFDACP TYPE(*ACCPTH) QAFDBASI QWHFDBAS TYPE(*BASATR) QAFDCSEQ QWHFDSEQ TYPE(*SEQ) QAFDJOIN QWHFDJN TYPE(*JOIN) QAFDMBR QWHFDMBR TYPE(*MBR) QAFDMBRL QWHFDML TYPE(*MBRLIST) QAFDRFMT QWHFDFMT TYPE(*RCDFMT) QAFDSELO QWHFDSO TYPE(*SELECT) QAFDSPOL QWHFDSPL TYPE(*SPOOL) QAFDBSC QWHFDBSC TYPE(*ATR) FILEATR(*BSCF) QAFDCMN QWHFDCMN TYPE(*ATR) FILEATR(*CMNF) QAFDDDM QWHFDDDM TYPE(*ATR) FILEATR(QWHFDDDM) QAFDDKT QWHFDDKT TYPE(*ATR) FILEATR(*DKTF) QAFDDSP QWHFDDSP TYPE(*ATR) FILEATR(*DSPF) QAFDICF QWHFDICF TYPE(*ATR) FILEATR(*ICFF) QAFDLGL QWHFDLGL TYPE(*ATR) FILEATR(*LF) QAFDPHY QWHFDPHY TYPE(*ATR) FILEATR(*PF) QAFDPRT QWHFDPRT TYPE(*ATR) FILEATR(*PRTF) QAFDSAV QWHFDSAV TYPE(*ATR) FILEATR(*SAVF) QAFDTAP QWHFDTAP TYPE(*ATR) FILEATR(*TAPF) DSPFLR QADSPDOC DOCDTL TYPE(*DOC) QADSPFLR FLRDTL TYPE(*FLR) DSPHDWRSC QARZDCMN QRZDCMN TYPE(*CMN) QARZDLWS QRZDLWS TYPE(*LWS) QARZDPRC QRZDPRC TYPE(*PRC) QARZDSTG QRZDSTG TYPE(*STG) QARZDTRA QRZDTRA TYPE(*TRA) DSPLCLHDW QARZHWOF QARZHDWD DSPJRN QADSPJRN QJORDJE OUTFILFMT(*TYPE1) QADSPJR2 QJORDJE2 OUTFILFMT(*TYPE2) QADSPJR3 QJORDJE3 OUTFILFMT(*TYPE3) QAWCTPJE QAWCTPJE JRNCDE(P) ENTTYP(TP) QADXERLG QDXERLOG JRNCDE(S) ENTTYP(XE) QADXJRNL QDXLGLOG JRNCDE(S) ENTTYP(XL) QASYAFJE QASYAFJE JRNCDE(T) ENTTYP(AF) QASYCAJE QASYCAJE JRNCDE(T) ENTTYP(CA) QASYCPJE QASYCPJE JRNCDE(T) ENTTYP(CP) QASYDOJE QASYDOJE JRNCDE(T) ENTTYP(DO) QASYDSJE QASYDSJE JRNCDE(T) ENTTYP(DS) QASYJDJE QASYJDJE JRNCDE(T) ENTTYP(JD) QASYNAJE QASYNAJE JRNCDE(T) ENTTYP(NA) QASYOWJE QASYOWJE JRNCDE(T) ENTTYP(OW) QASYPAJE QASYPAJE JRNCDE(T) ENTTYP(PA) QASYPSJE QASYPSJE JRNCDE(T) ENTTYP(PS) QASYPWJE QASYPWJE JRNCDE(T) ENTTYP(PW) QASYRAJE QASYRAJE JRNCDE(T) ENTTYP(RA) QASYRJJE QASYRJJE JRNCDE(T) ENTTYP(RJ) QASYROJE QASYROJE JRNCDE(T) ENTTYP(RO) QASYRPJE QASYRPJE JRNCDE(T) ENTTYP(RP) QASYRUJE QASYRUJE JRNCDE(T) ENTTYP(RU) QASYSEJE QASYSEJE JRNCDE(T) ENTTYP(SE) QASYSVJE QASYSVJE JRNCDE(T) ENTTYP(SV) QAJBACG QWTJAJBE QAPTACG QSPJAPTE QAZDALLG QZALLLOG (not in QSYS) QAZDCFLG QZDCFLOG QAZDERLG QZDERLOG QAZDJRNL QZDLGLOG QAZDRTLG QZDRTLOG DSPOBJAUT QAOBJAUT QSYDSAUT DSPOBJD QADSPOBJ QLIDOBJD DSPPGMADP QADPGMAD QADPGMAD DSPPGMREF QADSPPGM QWHDRPPR DSPPRB QASXPBOF QSXPBOF TYPE(*BASIC) QASXCAOF QSXCAOF TYPE(*CAUSE) QASXFXOF QSXFXOF TYPE(*FIX) QASXTXOF QSXTXOF TYPE(*USRTXT) QASXSDOF QSXSDOF TYPE(*SPTDTA) DSPPTF QADSPPTF QSCPTF DSPSFWRSC QARZLCOF QARZLCGD DSPUSRPRF QADSPUPA QSYDSUPA PRTDOC QAOPOUFL RECORD PRTERRLOG QAPRTELG QSCELOG QRYDOCLIB QAOSIQDL OSQDL QRYDST QAOSILIN OSLIN OPTION(*IN) QAOSILOT OSLOUT OPTION(*OUT) RCVDST QAOSIRCV OSRVCD RTVDOC QAOSIRTV OSRTVD RUNQRY (based on Query request) SAVDLO QAOJSAVO OJSDLO STRCPYSCN QASCCPY OSCCPY1 TRICF TQAIFTRCF QIFTRC TRCJOB QATRCJOB QSCTJTRC WRKNETF QANFDNTF QNFDNTF 
Getting Into Outfiles

Figure 2 QUSRTOOL CVT commands

 Figure 2: QUSRTOOL CVT Commands Model Format Command Description File Name CVTALLJOBQ Convert all job queues ALLJOBQP AJRCD CVTALLOUTQ Convert all output queues ALLOUTQP AORCD CVTCFGSTS Convert configuration status CFGSTSP CFRCD CVTDSKSTS Convert disk status DSKSTSP DSRCD CVTJOBQ Convert job queue JOBQP JQRCD CVTJRNA Convert journal attributes JRNFILP JRNFILR JRNACPP JRNACPR JRNRCVP JRNRCVR CVTJRNRCVA Convert journal receiver attributes JRNRCVAP JRNRCVAR CVTMSGF Convert message file MSGFP MSGFR CVTOBJLCK Convert object locks OBJLCKP OBJLCKR CVTOUTQ Convert output queue OUTQP SPLREC CVTPGMA Convert program attributes PGMATRP PGRCD CVTQHST Convert QHST file QHSTP QHSTR CVTSAVFD Convert SAVF description SAVFDP SAVFDR CVTSYSSTS Convert system status SYSSTSP SSRCD CVTTAPSAVD Convert tape save description TAPSAVDP TAPSAVDR CVTVOLSTAT Convert volume statistics VOLSTATP VOLSTATR CVTWRKACT Convert WRKACTJOB WRKACTP WRKACTR CVTWRKSBS Convert WRKSBS WRKSBSP WRKSBSR CVTWRKSPLF Convert WRKSPLF WRKSPLFP SFREC CVTWRKUSR Convert WRKUSRJOB WRKUSRP UJRCD 
Getting Into Outfiles

Figure 3 Sample listing of DSPFFD

 Figure 3: Sample Listing of DSPFFD 5738SS1 V2R1M1 920306 Display File Field Description Input parameters File . . . . . . . . . . . . . . . . . . . : QADSPOBJ Library . . . . . . . . . . . . . . . . . : *LIBL File Information File . . . . . . . . . . . . . . . . . . . : QADSPOBJ Library . . . . . . . . . . . . . . . . . : QSYS File location . . . . . . . . . . . . . . . : *LCL Externally described . . . . . . . . . . . : Yes Number of record formats . . . . . . . . . : 1 Type of file . . . . . . . . . . . . . . . : Physical File creation date . . . . . . . . . . . . : 10/22/90 Text 'description'. . . . . . . . . . . . . : System supplied outfile for DSPOBJD command. Record Format Information Record format . . . . . . . . . . . . . . . : QLIDOBJD Format level identifier . . . . . . . . . . : 3DE02B8DA1EA0 Number of fields . . . . . . . . . . . . . : 75 Record length . . . . . . . . . . . . . . . : 471 Format text . . . . . . . . . . . . . . . . : Object description Field Level Information Data Field Buffer Buffer Field Column Field Type Length Length Position Usage Heading ODDCEN CHAR 1 1 1 Both Display Century Field text . . . . . . . . . . . . . . . : Display century Coded Character Set Identifier . . . . . : 65535 ODDDAT CHAR 6 6 2 Both Display Date Field text . . . . . . . . . . . . . . . : Display date: format- Job date format Coded Character Set Identifier . . . . . : 65535 ODDTIM CHAR 6 6 8 Both Display Time Field text . . . . . . . . . . . . . . . : Display time Coded Character Set Identifier . . . . . : 65535 ODLBNM CHAR 10 10 14 Both Library Field text . . . . . . . . . . . . . . . : Library Coded Character Set Identifier . . . . . : 65535 ODOBNM CHAR 10 10 24 Both Object Field text . . . . . . . . . . . . . . . : Object Coded Character Set Identifier . . . . . : 65535 
Getting Into Outfiles

Figure 4 DDS for adding a key to an existing format

 Figure 4: DDS for Adding a Key to an Existing Format ... 1 ...+... 2 ...+... 3 ...+... 4 ...+... 5 ... 6 ...+... 7 A* FILE FOR DSPFFD - KEYED ON -LIB/FILE/FIELD A R QWHDRFFD FORMAT(QADSPFFD) A K WHLIB A K WHFILE A K WHFLDI ... 1 ...+... 2 ...+... 3 ...+... 4 ...+... 5 ... 6 ...+... 7 
Getting Into Outfiles

Figure 5 Examples of using outfiles in MC articles

 Figure 5: Examples of Using Outfiles in Midrange Computing Articles July 1992 Selective Clear Output Queue Command, CVTOUTQ June 1992 Under New Ownership, DSPOBJD Get a Handle on Object Authorities, DSPOBJD, DSPOBJAUT What Programs Use a File (Tech Talk), DSPOBJD, DSPPGMREF Files in CL (Tech Talk), DSPOBJD (CL shell for processing files) May 1992 Reorganize Your Data Queues, DSPOBJAUT 
BLOG COMMENTS POWERED BY DISQUS

LATEST COMMENTS

RESOURCE CENTER

  • WHITE PAPERS

  • WEBCAST

  • TRIAL SOFTWARE

  • Mobile Computing and the IBM i

    SB ASNA PPL 5450Mobile computing is rapidly maturing into a solid platform for delivering enterprise applications. Many IBM i shops today are realizing that integrating their IBM i with mobile applications is the fast path to improved business workflows, better customer relations, and more responsive business reporting.

    This ASNA whitepaper takes a look at mobile computing for the IBM i. It discusses the different ways mobile applications may be used within the enterprise and how ASNA products solve the challenges mobile presents. It also presents the case that you already have the mobile programming team your projects need: that team is your existing RPG development team!

    Get your copy today!

  • Automate IBM i Operations using Wireless Devices

    DDL SystemsDownload the technical whitepaper on MANAGING YOUR IBM i WIRELESSLY and (optionally) register to download an absolutely FREE software trail. This whitepaper provides an in-depth review of the native IBM i technology and ACO MONITOR's advanced two-way messaging features to remotely manage your IBM i while in or away from the office. Notify on-duty personnel of system events and remotely respond to complex problems (via your Smartphone) before they become critical-24/7. Problem solved!

    Order your copy here.

  • DR Strategy Guide from Maxava: Brand New Edition - now fully updated to include Cloud!

    SB Maxava PPL 5476PRACTICAL TOOLS TO IMPLEMENT DISASTER RECOVERY IN YOUR IBM i ENVIRONMENT

    CLOUD VS. ON-PREMISE?
    - COMPREHENSIVE CHECKLISTS
    - RISK COST CALCULATIONS
    - BUSINESS CASE FRAMEWORK
    - DR SOLUTIONS OVERVIEW
    - RFP BUILDER
    Download your free copy of DR Strategy Guide for IBM i from Maxava today.

     

  • White Paper: Node.js for Enterprise IBM i Modernization

    SB Profound WP 5539

    If your business is thinking about modernizing your legacy IBM i (also known as AS/400 or iSeries) applications, you will want to read this white paper first!

    Download this paper and learn how Node.js can ensure that you:
    - Modernize on-time and budget - no more lengthy, costly, disruptive app rewrites!
    - Retain your IBM i systems of record
    - Find and hire new development talent
    - Integrate new Node.js applications with your existing RPG, Java, .Net, and PHP apps
    - Extend your IBM i capabilties to include Watson API, Cloud, and Internet of Things


    Read Node.js for Enterprise IBM i Modernization Now!

     

  • 2020 IBM i Marketplace Survey Results

    HelpSystems

    This year marks the sixth edition of the popular IBM i Marketplace Survey Results. Each year, HelpSystems sets out to gather data about how businesses use the IBM i platform and the IT initiatives it supports. Year over year, the survey has begun to reveal long-term trends that give insight into the future of this trusted technology.

    More than 500 IBM i users from around the globe participated in this year’s survey, and we’re so happy to share the results with you. We hope you’ll find the information interesting and useful as you evaluate your own IT projects.

  • AIX Security Basics eCourse

    Core Security

    With so many organizations depending on AIX day to day, ensuring proper security and configuration is critical to ensure the safety of your environment. Don’t let common threats put your critical AIX servers at risk. Avoid simple mistakes and start to build a long-term plan with this AIX Security eCourse. Enroll today to get easy to follow instructions on topics like:

    • Removing extraneous files
    • Patching systems efficiently
    • Setting and validating permissions
    • Managing service considerations
    • Getting overall visibility into your networks

     

  • Developer Kit: Making a Business Case for Modernization and Beyond

    Profound Logic Software, Inc.

    Having trouble getting management approval for modernization projects? The problem may be you're not speaking enough "business" to them.

    This Developer Kit provides you study-backed data and a ready-to-use business case template to help get your very next development project approved!

  • What to Do When Your AS/400 Talent Retires

    HelpSystemsIT managers hoping to find new IBM i talent are discovering that the pool of experienced RPG programmers and operators or administrators is small.

    This guide offers strategies and software suggestions to help you plan IT staffing and resources and smooth the transition after your AS/400 talent retires. Read on to learn:

    • Why IBM i skills depletion is a top concern
    • How leading organizations are coping
    • Where automation will make the biggest impact

     

  • IBM i Resources Retiring?

    SB HelpSystems WC GenericLet’s face it: IBM i experts and RPG programmers are retiring from the workforce. Are you prepared to handle their departure?
    Our panel of IBM i experts—Chuck Losinski, Robin Tatam, Richard Schoen, and Tom Huntington—will outline strategies that allow your company to cope with IBM i skills depletion by adopting these strategies that allow you to get the job done without deep expertise on the OS:
    - Automate IBM i processes
    - Use managed services to help fill the gaps
    - Secure the system against data loss and viruses
    The strategies you discover in this webinar will help you ensure that your system of record—your IBM i—continues to deliver a powerful business advantage, even as staff retires.

     

  • Backup and Recovery Considerations for Security Data and Encrypted Backups

    SB PowerTech WC GenericSecurity expert Carol Woodbury is joined by Debbie Saugen. Debbie is an expert on IBM i backup and recovery, disaster recovery, and high availability, helping IBM i shops build and implement effective business continuity plans.
    In today’s business climate, business continuity is more important than ever. But 83 percent of organizations are not totally confident in their backup strategy.
    During this webinar, Carol and Debbie discuss the importance of a good backup plan, how to ensure you’re backing up your security information, and your options for encrypted back-ups.

  • Profound.js: The Agile Approach to Legacy Modernization

    SB Profound WC GenericIn this presentation, Alex Roytman and Liam Allan will unveil a completely new and unique way to modernize your legacy applications. Learn how Agile Modernization:
    - Uses the power of Node.js in place of costly system re-writes and migrations
    - Enables you to modernize legacy systems in an iterative, low-risk manner
    - Makes it easier to hire developers for your modernization efforts
    - Integrates with Profound UI (GUI modernization) for a seamless, end-to-end legacy modernization solution

     

  • Data Breaches: Is IBM i Really at Risk?

    SB PowerTech WC GenericIBM i is known for its security, but this OS could be more vulnerable than you think.
    Although Power Servers often live inside the safety of the perimeter firewall, the risk of suffering a data leak or data corruption remains high.
    Watch noted IBM i security expert Robin Tatam as he discusses common ways that this supposedly “secure” operating system may actually be vulnerable and who the culprits might be.

    Watch the webinar today!

     

  • Easy Mobile Development

    SB Profound WC GenericWatch this on-demand webinar and learn how to rapidly and easily deploy mobile apps to your organization – even when working with legacy RPG code! IBM Champion Scott Klement will demonstrate how to:
    - Develop RPG applications without mobile development experience
    - Deploy secure applications for any mobile device
    - Build one application for all platforms, including Apple and Android
    - Extend the life and reach of your IBM i (aka iSeries, AS400) platform
    You’ll see examples from customers who have used our products and services to deliver the mobile applications of their dreams, faster and easier than they ever thought possible!

     

  • Profound UI: Unlock True Modernization from your IBM i Enterprise

    SB Profound PPL 5491Modern, web-based applications can make your Enterprise more efficient, connected and engaged. This session will demonstrate how the Profound UI framework is the best and most native way to convert your existing RPG applications and develop new modern applications for your business. Additionally, you will learn how you can address modernization across your Enterprise, including databases and legacy source code, with Profound Logic.

  • Node Webinar Series Pt. 1: The World of Node.js on IBM i

    Profound Logic Software, Inc.Have you been wondering about Node.js? Our free Node.js Webinar Series takes you from total beginner to creating a fully-functional IBM i Node.js business application.

    Part 1 will teach you what Node.js is, why it's a great option for IBM i shops, and how to take advantage of the ecosystem surrounding Node.

    In addition to background information, our Director of Product Development Scott Klement will demonstrate applications that take advantage of the Node Package Manager (npm).

  • 5 New and Unique Ways to Use the IBM i Audit Journal

    SB HelpSystems ROBOT GenericYou must be asking yourself: am I doing everything I can to protect my organization’s data? Tune in as our panel of IBM i high availability experts discuss:


    - Why companies don’t test role swaps when they know they should
    - Whether high availability in the cloud makes sense for IBM i users
    - Why some organizations don’t have high availability yet
    - How to get high availability up and running at your organization
    - High availability considerations for today’s security concerns

  • Profound.js 2.0: Extend the Power of Node to your IBM i Applications

    SB Profound WC 5541In this Webinar, we'll demonstrate how Profound.js 2.0 enables you to easily adopt Node.js in your business, and to take advantage of the many benefits of Node, including access to a much larger pool of developers for IBM i and access to countless reusable open source code packages on npm (Node Package Manager).
    You will see how Profound.js 2.0 allows you to:

    • Provide RPG-like capabilities for server-side JavaScript.
    • Easily create web and mobile application interfaces for Node on IBM i.
    • Let existing RPG programs call Node.js modules directly, and vice versa.
    • Automatically generate code for Node.js.
    • Automatically converts existing RPGLE code into clean, simplified Node.js code.

    Download and watch today!

     

  • Make Modern Apps You'll Love with Profound UI & Profound.js

    SB Profound WC 5541Whether you have green screens or a drab GUI, your outdated apps can benefit from modern source code, modern GUIs, and modern tools.
    Profound Logic's Alex Roytman and Liam Allan are here to show you how Free-format RPG and Node.js make it possible to deliver applications your whole business will love:

    • Transform legacy RPG code to modern free-format RPG and Node.js
    • Deliver truly modern application interfaces with Profound UI
    • Extend your RPG applications to include Web Services and NPM packages with Node.js

     

  • Accelerating Programmer Productivity with Sequel

    SB_HelpSystems_WC_Generic

    Most business intelligence tools are just that: tools, a means to an end but not an accelerator. Yours could even be slowing you down. But what if your BI tool didn't just give you a platform for query-writing but also improved programmer productivity?
    Watch the recorded webinar to see how Sequel:

    • Makes creating complex results simple
    • Eliminates barriers to data sources
    • Increases flexibility with data usage and distribution

    Accelerated productivity makes everyone happy, from programmer to business user.

  • Business Intelligence is Changing: Make Your Game Plan

    SB_HelpSystems_WC_GenericIt’s time to develop a strategy that will help you meet your informational challenges head-on. Watch the webinar to learn how to set your IT department up for business intelligence success. You’ll learn how the right data access tool will help you:

    • Access IBM i data faster
    • Deliver useful information to executives and business users
    • Empower users with secure data access

    Ready to make your game plan and finally keep up with your data access requests?

     

  • Controlling Insider Threats on IBM i

    SB_HelpSystems_WC_GenericLet’s face facts: servers don’t hack other servers. Despite the avalanche of regulations, news headlines remain chock full of stories about data breaches, all initiated by insiders or intruders masquerading as insiders.
    User profiles are often duplicated or restored and are rarely reviewed for the appropriateness of their current configuration. This increases the risk of the profile being able to access data without the intended authority or having privileges that should be reserved for administrators.
    Watch security expert Robin Tatam as he discusses a new approach for onboarding new users on IBM i and best-practices techniques for managing and monitoring activities after they sign on.

  • Don't Just Settle for Query/400...

    SB_HelpSystems_WC_GenericWhile introducing Sequel Data Access, we’ll address common frustrations with Query/400, discuss major data access, distribution trends, and more advanced query tools. Plus, you’ll learn how a tool like Sequel lightens IT’s load by:

    - Accessing real-time data, so you can make real-time decisions
    - Providing run-time prompts, so users can help themselves
    - Delivering instant results in Microsoft Excel and PDF, without the wait
    - Automating the query process with on-demand data, dashboards, and scheduled jobs

  • How to Manage Documents the Easy Way

    SB_HelpSystems_WC_GenericWhat happens when your company depends on an outdated document management strategy?
    Everything is harder.
    You don’t need to stick with status quo anymore.
    Watch the webinar to learn how to put effective document management into practice and:

    • Capture documents faster, instead of wasting everyone’s time
    • Manage documents easily, so you can always find them
    • Distribute documents automatically, and move on to the next task

     

  • Lessons Learned from the AS/400 Breach

    SB_PowerTech_WC_GenericGet actionable info to avoid becoming the next cyberattack victim.
    In “Data breach digest—Scenarios from the field,” Verizon documented an AS/400 security breach. Whether you call it AS/400, iSeries, or IBM i, you now have proof that the system has been breached.
    Watch IBM i security expert Robin Tatam give an insightful discussion of the issues surrounding this specific scenario.
    Robin will also draw on his extensive cybersecurity experience to discuss policies, processes, and configuration details that you can implement to help reduce the risk of your system being the next victim of an attack.

  • Overwhelmed by Operating Systems?

    SB_HelpSystems_WC_GenericIn this 30-minute recorded webinar, our experts demonstrate how you can:

    • Manage multiple platforms from a central location
    • View monitoring results in a single pane of glass on your desktop or mobile device
    • Take advantage of best practice, plug-and-play monitoring templates
    • Create rules to automate daily checks across your entire infrastructure
    • Receive notification if something is wrong or about to go wrong

    This presentation includes a live demo of Network Server Suite.

     

  • Real-Time Disk Monitoring with Robot Monitor

    SB_HelpSystems_WC_GenericYou need to know when IBM i disk space starts to disappear and where it has gone before system performance and productivity start to suffer. Our experts will show you how Robot Monitor can help you pinpoint exactly when your auxiliary storage starts to disappear and why, so you can start taking a proactive approach to disk monitoring and analysis. You’ll also get insight into:

    • The main sources of disk consumption
    • How to monitor temporary storage and QTEMP objects in real time
    • How to monitor objects and libraries in real time and near-real time
    • How to track long-term disk trends

     

     

  • Stop Re-keying Data Between IBM I and Other Applications

    SB_HelpSystems_WC_GenericMany business still depend on RPG for their daily business processes and report generation.Wouldn’t it be nice if you could stop re-keying data between IBM i and other applications? Or if you could stop replicating data and start processing orders faster? Or what if you could automatically extract data from existing reports instead of re-keying? It’s all possible. Watch this webinar to learn about:

    • The data dilemma
    • 3 ways to stop re-keying data
    • Data automation in practice

    Plus, see how HelpSystems data automation software will help you stop re-keying data.

     

  • The Top Five RPG Open Access Myths....BUSTED!

    SB_Profound_WC_GenericWhen it comes to IBM Rational Open Access: RPG Edition, there are still many misconceptions - especially where application modernization is concerned!

    In this Webinar, we'll address some of the biggest myths about RPG Open Access, including:

    • Modernizing with RPG OA requires significant changes to the source code
    • The RPG language is outdated and impractical for modernizing applications
    • Modernizing with RPG OA is the equivalent to "screen scraping"

     

  • Time to Remove the Paper from Your Desk and Become More Efficient

    SB_HelpSystems_WC_GenericToo much paper is wasted. Attempts to locate documents in endless filing cabinets.And distributing documents is expensive and takes up far too much time.
    These are just three common reasons why it might be time for your company to implement a paperless document management system.
    Watch the webinar to learn more and discover how easy it can be to:

    • Capture
    • Manage
    • And distribute documents digitally

     

  • IBM i: It’s Not Just AS/400

    SB_HelpSystems_WC_Generic

    IBM’s Steve Will talks AS/400, POWER9, cognitive systems, and everything in between

    Are there still companies that use AS400? Of course!

    IBM i was built on the same foundation.
    Watch this recorded webinar with IBM i Chief Architect Steve Will and IBM Power Champion Tom Huntington to gain a unique perspective on the direction of this platform, including:

    • IBM i development strategies in progress at IBM
    • Ways that Watson will shake hands with IBM i
    • Key takeaways from the AS/400 days

     

  • Ask the RDi Experts

    SB_HelpSystems_WC_GenericWatch this recording where Jim Buck, Susan Gantner, and Charlie Guarino answered your questions, including:

    • What are the “hidden gems” in RDi that can make me more productive?
    • What makes RDi Debug better than the STRDBG green screen debugger?
    • How can RDi help me find out if I’ve tested all lines of a program?
    • What’s the best way to transition from PDM to RDi?
    • How do I convince my long-term developers to use RDi?

    This is a unique, online opportunity to hear how you can get more out of RDi.

     

  • Node.js on IBM i Webinar Series Pt. 2: Setting Up Your Development Tools

    Profound Logic Software, Inc.Have you been wondering about Node.js? Our free Node.js Webinar Series takes you from total beginner to creating a fully-functional IBM i Node.js business application. In Part 2, Brian May teaches you the different tooling options available for writing code, debugging, and using Git for version control. Attend this webinar to learn:

    • Different tools to develop Node.js applications on IBM i
    • Debugging Node.js
    • The basics of Git and tools to help those new to it
    • Using NodeRun.com as a pre-built development environment

     

     

  • Inside the Integrated File System (IFS)

    SB_HelpSystems_WC_GenericDuring this webinar, you’ll learn basic tips, helpful tools, and integrated file system commands—including WRKLNK—for managing your IFS directories and Access Client Solutions (ACS). We’ll answer your most pressing IFS questions, including:

    • What is stored inside my IFS directories?
    • How do I monitor the IFS?
    • How do I replicate the IFS or back it up?
    • How do I secure the IFS?

    Understanding what the integrated file system is and how to work with it must be a critical part of your systems management plans for IBM i.

     

  • Expert Tips for IBM i Security: Beyond the Basics

    SB PowerTech WC GenericIn this session, IBM i security expert Robin Tatam provides a quick recap of IBM i security basics and guides you through some advanced cybersecurity techniques that can help you take data protection to the next level. Robin will cover:

    • Reducing the risk posed by special authorities
    • Establishing object-level security
    • Overseeing user actions and data access

    Don't miss this chance to take your knowledge of IBM i security beyond the basics.

     

     

  • 5 IBM i Security Quick Wins

    SB PowerTech WC GenericIn today’s threat landscape, upper management is laser-focused on cybersecurity. You need to make progress in securing your systems—and make it fast.
    There’s no shortage of actions you could take, but what tactics will actually deliver the results you need? And how can you find a security strategy that fits your budget and time constraints?
    Join top IBM i security expert Robin Tatam as he outlines the five fastest and most impactful changes you can make to strengthen IBM i security this year.
    Your system didn’t become unsecure overnight and you won’t be able to turn it around overnight either. But quick wins are possible with IBM i security, and Robin Tatam will show you how to achieve them.

  • How to Meet the Newest Encryption Requirements on IBM i

    SB PowerTech WC GenericA growing number of compliance mandates require sensitive data to be encrypted. But what kind of encryption solution will satisfy an auditor and how can you implement encryption on IBM i? Watch this on-demand webinar to find out how to meet today’s most common encryption requirements on IBM i. You’ll also learn:

    • Why disk encryption isn’t enough
    • What sets strong encryption apart from other solutions
    • Important considerations before implementing encryption

     

     

  • Security Bulletin: Malware Infection Discovered on IBM i Server!

    SB PowerTech WC GenericMalicious programs can bring entire businesses to their knees—and IBM i shops are not immune. It’s critical to grasp the true impact malware can have on IBM i and the network that connects to it. Attend this webinar to gain a thorough understanding of the relationships between:

    • Viruses, native objects, and the integrated file system (IFS)
    • Power Systems and Windows-based viruses and malware
    • PC-based anti-virus scanning versus native IBM i scanning

    There are a number of ways you can minimize your exposure to viruses. IBM i security expert Sandi Moore explains the facts, including how to ensure you're fully protected and compliant with regulations such as PCI.

     

     

  • Fight Cyber Threats with IBM i Encryption

    SB PowerTech WC GenericCyber attacks often target mission-critical servers, and those attack strategies are constantly changing. To stay on top of these threats, your cybersecurity strategies must evolve, too. In this session, IBM i security expert Robin Tatam provides a quick recap of IBM i security basics and guides you through some advanced cybersecurity techniques that can help you take data protection to the next level. Robin will cover:

    • Reducing the risk posed by special authorities
    • Establishing object-level security
    • Overseeing user actions and data access

     

     

     

  • 10 Practical IBM i Security Tips for Surviving Covid-19 and Working From Home

    SB PowerTech WC GenericNow that many organizations have moved to a work from home model, security concerns have risen.

    During this session Carol Woodbury will discuss the issues that the world is currently seeing such as increased malware attacks and then provide practical actions you can take to both monitor and protect your IBM i during this challenging time.

     

  • How to Transfer IBM i Data to Microsoft Excel

    SB_HelpSystems_WC_Generic3 easy ways to get IBM i data into Excel every time
    There’s an easy, more reliable way to import your IBM i data to Excel? It’s called Sequel. During this webinar, our data access experts demonstrate how you can simplify the process of getting data from multiple sources—including Db2 for i—into Excel. Watch to learn how to:

    • Download your IBM i data to Excel in a single step
    • Deliver data to business users in Excel via email or a scheduled job
    • Access IBM i data directly using the Excel add-in in Sequel

    Make 2020 the year you finally see your data clearly, quickly, and securely. Start by giving business users the ability to access crucial business data from IBM i the way they want it—in Microsoft Excel.

     

     

  • HA Alternatives: MIMIX Is Not Your Only Option on IBM i

    SB_HelpSystems_WC_GenericIn this recorded webinar, our experts introduce you to the new HA transition technology available with our Robot HA software. You’ll learn how to:

    • Transition your rules from MIMIX (if you’re happy with them)
    • Simplify your day-to-day activities around high availability
    • Gain back time in your work week
    • Make your CEO happy about reducing IT costs

    Don’t stick with a legacy high availability solution that makes you uncomfortable when transitioning to something better can be simple, safe, and cost-effective.

     

     

  • Comply in 5! Well, actually UNDER 5 minutes!!

    SB CYBRA PPL 5382

    TRY the one package that solves all your document design and printing challenges on all your platforms.

    Produce bar code labels, electronic forms, ad hoc reports, and RFID tags – without programming! MarkMagic is the only document design and print solution that combines report writing, WYSIWYG label and forms design, and conditional printing in one integrated product.

    Request your trial now!

  • Backup and Recovery on IBM i: Your Strategy for the Unexpected

    SB HelpSystems SC 5413Robot automates the routine tasks of iSeries backup and recovery, saving you time and money and making the process safer and more reliable. Automate your backups with the Robot Backup and Recovery Solution. Key features include:
    - Simplified backup procedures
    - Easy data encryption
    - Save media management
    - Guided restoration
    - Seamless product integration
    Make sure your data survives when catastrophe hits. Try the Robot Backup and Recovery Solution FREE for 30 days.

  • Manage IBM i Messages by Exception with Robot

    SB HelpSystems SC 5413Managing messages on your IBM i can be more than a full-time job if you have to do it manually. How can you be sure you won’t miss important system events?
    Automate your message center with the Robot Message Management Solution. Key features include:
    - Automated message management
    - Tailored notifications and automatic escalation
    - System-wide control of your IBM i partitions
    - Two-way system notifications from your mobile device
    - Seamless product integration
    Try the Robot Message Management Solution FREE for 30 days.

  • Easiest Way to Save Money? Stop Printing IBM i Reports

    SB HelpSystems SC 5413Robot automates report bursting, distribution, bundling, and archiving, and offers secure, selective online report viewing.
    Manage your reports with the Robot Report Management Solution. Key features include:

    - Automated report distribution
    - View online without delay
    - Browser interface to make notes
    - Custom retention capabilities
    - Seamless product integration
    Rerun another report? Never again. Try the Robot Report Management Solution FREE for 30 days.

  • Hassle-Free IBM i Operations around the Clock

    SB HelpSystems SC 5413For over 30 years, Robot has been a leader in systems management for IBM i.
    Manage your job schedule with the Robot Job Scheduling Solution. Key features include:
    - Automated batch, interactive, and cross-platform scheduling
    - Event-driven dependency processing
    - Centralized monitoring and reporting
    - Audit log and ready-to-use reports
    - Seamless product integration
    Scale your software, not your staff. Try the Robot Job Scheduling Solution FREE for 30 days.

  • ACO MONITOR Manages your IBM i 24/7 and Notifies You When Your IBM i Needs Assistance!

    SB DDL Systems 5429More than a paging system - ACO MONITOR is a complete systems management solution for your Power Systems running IBM i. ACO MONITOR manages your Power System 24/7, uses advanced technology (like two-way messaging) to notify on-duty support personnel, and responds to complex problems before they reach critical status.

    ACO MONITOR is proven technology and is capable of processing thousands of mission-critical events daily. The software is pre-configured, easy to install, scalable, and greatly improves data center efficiency.