Each tool is described in a short summary on this page. The tools are listed in alphabetical order.
The Abort command is designed for use in a HLL program to end the program by sending the TAA9861 message as an escape. ABORT is both a command and a program name. An intended use of the program is when a CALL error has occurred and you want to recover from one or more specific error conditions, but not others. After handling the specific error conditions, just call ABORT.
Access Secure Library. Allows a method by which programmers can be kept from changing anything in a secure library, but are allowed to display, copy or use CRTDUPOBJ to their own library. The Security Officer must specify which libraries can be accessed.
The Activate Deleted Record command writes an initialized record to a physical file relative record number. The record must be in a deleted status. This makes an active record in the file that can then be updated by other functions. The companion command is DLTACTRCD which deletes an active record.
Add Binary 4 Values. This command is useful in CL programs when dealing with user spaces. It allows you to add two 4 byte character fields (which are really binary values) and produce a 4 byte binary result. The tool exists only for compatibility purposes as CL now supports the %BIN function.
Add Date. Adds or subtracts a number of days from the system date or a named date and returns the new date. Useful for any scheduling function involving dates.
The Add Date Member command adds a new member to a multi-member file using the name MCYYMMDDnn where CYYMMDD is the current date and nn is a consecutive number beginning with 01. Up to 99 versions may exist for a single day and a maximum of 32,767 members in the file. A return value exists for the member name that was assigned.
The Add Date 2 command allows a number of days to be add or subtracted from any date. Both the From date format and the To date format may be in any of the system supported date types. The command is useful for determining expiration dates or any other form of scheduling.
The Add Date 3 command allows a number of days to be added or subtracted from a date and returns a new date. ADDDAT3 is similar to ADDDAT2, but has been optimized for new dates in the same year as the input date. The number of days parameter is limited to -365 to +365. Any date format may be input and output.
The Add Default Record command allows the insertion of default records at the beginning, the middle, or at the end of a physical file. If the inserts occur before the end of the file, the relative record numbers of the remaining records are shifted down to new relative record numbers. The inserted record fields will be filled with blanks or zeros.
Add Distribution List Entry 2 assists with adding users to the same distribution lists to which another user belongs. If the user is already on one of the identified lists, no action is taken.
Add to a Data Area. Adds or subtracts a number to a data area. Useful for consecutively updating a data area such as ‘next order number’. Can be used from one job or multiple jobs. Allows a return variable with the number before the update. The data area must be defined as *DEC LEN(9 0).
The Add Group Profile command adds a Group Profile to one or more user profiles. The Group Profile is added either as the GRPPRF parameter or as a supplemental group (SUPGRPPRF parameter). A listing is output of the changes and any error conditions such as the profile is already specified as belonging to the group.
The Add Hexadecimal command adds or subtracts two hexadecimal or decimal values and returns either or both a hexadecimal or decimal value. Either unsigned or signed hex values may be entered. ADDHEX can be helpful when viewing dumps or user spaces.
The Add Initialized Record command adds one or more initialized records to an existing member of a physical file. Initialized records will have valid values in decimal fields, date fields, etc.
The Add Job Description library tool supports ADDJOBDLIB and RMVJOBDLIB to add or remove a single library from the INLLIBL parameter of one, all, or generic job descriptions in a library. A POSITION parameter similar to ADDLIBLE is supported. This simplifies mass changes to job descriptions or the simple step of adding or removing a library.
The Add Job Schedule 2 command adds one or more job schedule entries from the JOBSCDP file created by the CVTJOBSCDE TAA Tool to the system job scheduling function. A single job name may be added, a set of generic job names, or all names in a file. Using both CVTJOBSCDE and ADDJOBSCD2 allows system job schedule entries to be transported to another system.
The ADD PDM Options command adds a record for certain TAA Tool commands to the PDM Options file. This allows a simple 2 character entry to cause a TAA Tool command for a member or object in the same manner as the PDM supported options.
The Add Relational Data Base (RDB) command is intended to assist in moving RDB entries as seen with DSPRDBDIRE to a different system. You must first capture the RDB entries to an outfile with DSPRDBDIRE and then move the outfile to the system to be applied to. Duplicate RDB names are rejected as well as a second version of *LOCAL for the Remote Location Name.
The Add Reply List Entry 2 command uses the outfile created by CVTRPYLE on one system to allow individual entries to be added to another system. One entry at a time is added to the System Reply List. The command can make it easier to keep the System Reply Lists similar on multiple systems.
The Add Special Authority command allows the addition of a special authority to one or more profiles. This is a simpler interface than CHGUSRPRF which requires an entry for any existing authorities as well as a new special authority. A RMVSPCAUT command is also provided to remove a special authority from one or more profiles.
The Add Source Member command exists to allow for compatibility with an old version in QUSRTOOL. The function is no longer needed because ADDPFM now supports the SRCTYPE parameter.
The Add Supplemental Group command allows the adding of a supplemental group profile to one or more user profiles. The companion command is Remove Supplemental Group to remove a supplemental group profile from one or more user profiles.
Add to a Time Value. Adds or subtracts a number of seconds from the current time or a specified time. Returns the new time. Useful for scheduling functions involving time of day.
The Add Unique Member command adds a unique member to an existing data base file. The naming convention UNQnnnnnnn is used where nnnnnnn is a number in the range of 1 to 9,999,999. The maximum members in a file at one time may only be 32,767. A return value exists for the member name that was assigned. The text description parameter should contain the purpose of the member.
The Adjust Apostrophes command is designed to adjust the number of apostrophes in a variable so that the return result is valid for command processing. ADJAPOST is specifically designed for IFS processing, but may be used for variables intended for non-IFS use.
The Adjust Time command adjusts the time of day clock. The adjustment is specified either plus or minus in microseconds. The adjustment period occurs over a period of time such as it may take several minutes for a few seconds to be adjusted. The time for the adjustment to take place is also dependent on hardware speed. The QWCADJTM API is used.
Adjust variable. Provides a method of centering, left adjusting, or right adjusting data into a return variable. Useful for adjusting variable length headings before printing or displaying. For right adjusting a decimal value, see the RGTADJVAR tool.
Adopt member. Provides an alternative method of allowing end users to add, clear, or remove members during programs. Three commands are provided (ADDPFMADP, CLRPFMADP, and RMVMADP) which have the same parameters and options as the corresponding system commands. The Security Officer must define what files are valid to be used with the tool commands.
Allocate Data Base File. Allocates a data base file and all of it’s members. This differs from the normal ALCOBJ command which will allocate only a single member. A DLCDBF command also exists.
The Allocate Library command allows objects in one or more libraries to be locked in a similar manner to the system SAV commands. The function is not a complete match with the SAV function locking approach, but may be used as a pre-test condition to a SAV function. A spooled file and an outfile are created. The companion command is Deallocate Library (DLCLIB) to unlock the objects found in the outfile.
Allocate Object 2. Performs the same allocation as the system ALCOBJ command, but provides better feedback. A completion message is sent if the command is successful. If the object cannot be allocated, diagnostic messages are sent describing the jobs that hold the conflicting locks followed by an escape message.
Allocate Temporary Member. Allocates a member in files provided in TAATOOL and returns the member name. This is a performance advantage for those jobs which need to create temporary files (e.g. an outfile from a DSP command). The overhead of creating files and members is significant. ALCTMPMBR provides standard files which can be used and allocates members to individual jobs.
The Analyze CLP Commands command analyzes the CLP commands in the CLPCMDP file created by the CVTCLPCMD TAA tool. A summary by command name is listed. Selection can occur by such things as a source file name and library.
The Analyze Field command sequences an externally described file on a named field and allows analysis by percentiles, ranges, or unique values. For each summary line printed, decimal fields may be summed, averaged, the maximum and minimum values determined, and the standard deviation calculated. Selection criteria may be specified to limit what is processed.
The Analyze Output Queue command provides summary information for various attributes of spooled files in an output queue such as by form type, by user, by schedule, by open date, etc. For each category, a count is also supplied. ANZOUTQ provides a good summary of what exists.
The Analyze RPG Source command outputs a listing for a specific RPG or RPGLE source member. Some information is standard and is always output such as the number of comments and counts by spec type. Other information is optional such as where subroutines begin/end and an operation code summary. Both RPG III and RPG IV (fixed form) member types are supported.
The Analyze TAA Usage command analyzes information concerning TAA usage. The intent of the command is to provide feedback to Jim Sloan, Inc. regarding customer usage of TAA functions.
Application Value. The Application Value tool is designed to allow options to be specified for a standard application. Commands are provided for both the ‘application designer’ and the ‘application installer’. Useful for writing applications which need to have options that vary per installation.
The Apply Remote Journal tool provides ‘real time’ data replication to a remote system using the system remote journaling support. Only data from data base members, data areas, and data queues are supported. The function may be used for a variety of application needs. If used for high availability, you have the responsibility of keeping the environment in synch (such as changes to programs, object attributes, etc).
Apply User Change. APYUSRCHG takes the output file produced by DSPJRN and applies it to one or all user files. Useful for applying the journal to a duplicate file where the i5/OS APYJRNCHG command cannot be used or when the journal must be transmitted and is too large.
Attention Program. Simple attention key program which provides two group jobs. Simple flip/flop. Works with user profile ATNPGM parameter. Useful for any work requiring a second group job.
This is a documentation member only to help understand the basics of auditing on the system and some of the helpful TAA Tools. This provides an overview and some simple examples of how to get started with auditing.
The Audit Log tool is a series of commands that let you work with the audit log entries from the QAUDJRN journal. You may either display the entries using several different access paths or print the entries using different selection and sequencing criteria. Audit logs from multiple systems may be stored in the same data base.
Binary Search. An RPG technique to use a binary search instead of a normal lookup operation. On large arrays (e.g. 100+ entries), this can be a significant performance advantage.
Breakpoint Tool. Provides multiple commands for working with debug including BKP, TRACE, STEP, DBGVAR, and CHGDBGVAR. Simplifies using the debug facility by providing front end commands. Uses a data area in QTEMP and a prompt override program. Useful for debugging of programs.
Build Call. Allows a simple approach for submitting a CALL command to batch with a parameter list. The CMD parameter on SBMJOB eliminates much of the need for this function, but it is still useful in some cases.
The Build Check Amount tool is designed to print words for the amount on a check such as ‘Four hundred dollars and 03 cents’. A program is supplied to convert a decimal value to a string of text. An externally described data structure is used to pass the amount, return the string of text, and provide for various options. A demonstration of the function and options exists.
The Build Data Base File Override tool is a program that can be called to provide an OVRDBF command ready to execute using QCMDEXC. The values and return command are passed in an externally described data structure. This simplifies what a program has to do for the typical application that processes a member list.
Build Print Line. Used to build a formatted print line for the TAA tool PRINT. Avoids having to concatenate in blanks to provide for proper spacing while using the PRINT command. Allows editing of numeric values.
The Build Qualified Name command exists to allow for compatibility with an old version in QUSRTOOL. The function is no longer needed because RPG now supports a concatenation function.
The Build RPG message tool builds messages from array records in your RPG program. The message text can be used on displays, spooled output, or sent as message text. The tool describes how to use the standard code in your program to assist you in sending messages from an RPG program. The standard code is provided in TAARPGJR in QATTRPG.
The Blank System Message command allows you to blank out an existing message in a message file and rename the message ID. This is intended for bothersome messages such as EDT0630 (‘Have you tried the modern alternative to SEU?’). The message will continue to be sent, but only blanks will appear on the display. When BLKSYSMSG is used, a confirming display appears with the text of the message to be blanked out.
The Bombing Run command provides an interactive game where you attempt to bomb a target. A plane moves across the display after you press Enter. F6 is used to drop the bomb. You must account for the direction and maximum speed of the wind. The target is also moving.
Break message queue N times. This allows N users to be notified when a message arrives at a specific message queue. Any user can respond to inquiry messages. Only a single user (the user who has the queue in break mode) can delete messages.
The Business Calendar tool provides a solution for the question ‘How many working days exist between 2 dates?’. A ‘business calendar’ object (a *USRSPC) must be created. The definition of ‘working days’ is made by use of the WRKBUSCAL command which allows days to be ‘excluded’ such as ‘Saturday’, ‘Christmas’, or specific dates. WRKBUSCAL then builds a list of the ‘excluded’ and ‘included’ dates.
The Calculator tool is a series of commands that allow you to use the system as a simple add/sub calculator and provides an optional listing. The CLCFILP file must be created first. Many members may exist in the file thus allowing both temporary and permanent lists to be created and changed. Each amount entered may have an optional text description. The last date changed exists for each record.
Capture and Return Job Attributes. The two commands are intended to allow a user program to protect its job environment when a sub program is called that wants to establish its own environment (e.g. the library list). The CAPJOBA command allows all of the current job attributes to be stored in a data area in QTEMP. The subprogram is then called. On return, the RTNJOBA command is used to reset the job environment.
Capture network attributes. The CAPNETA command provides a method of capturing the network attributes and storing them in the NETWRKATTR data area in TAASECURE. The companion command RTNNETA returns the attributes found in NETWRKATTR (CHGNETA is used). Useful for hot site recovery situations or when the network attributes should be shipped to another system.
The Capture PTF Information tool allows you to periodically capture PTF information using the outfile from the system DSPPTF command. Each captured version becomes a separate member in the PTFINFP data base file. The CMPPTFINF command may then be used to compare the changes between different versions.
The Capture Security Information tool allows you to capture the current information for user profiles, system values, network attributes, and registration information. This allows a comparison to be made at a later time against the same information captured on a different date.
The Capture System Information tool provides a method of capturing all object, member, and IFS object information on a system. Each type of information is optional. Each time CAPSYSINF is run, new versions are added to files in a named library (the default name is TAASYSINF). These files can then be used by other TAA Tools such as CPYSYSINF or CMPSYSINF or queried by user functions.
The Change All Spooled Files command allows all spooled files in an output queue to be changed for such values as OUTQ, FORMTYPE, SAVE, and ALIGN. This provides a command interface instead of using the ‘2’ option on WRKOUTQ. A Hold/Release option also exists.
The Change ASP (Auxiliary Storage Pool) Attributes 2 command allows a user with the special authorities *SERVICE and *ALLOBJ to change an ASP threshold value and the Compression Recovery Policy.
The Change Authority 2 command is a simple front end to the system CHGAUT command that operates only on objects in a library. Multiple users may be specified, but not all CHGAUT functions are supported. Unlike GRT/RVKOBJAUT, there are no low level messages that clutter the job log and cannot be removed.
Change Big Parameter. Allows a job to pass a large parameter to a batch job. Up to 2000 bytes can be passed on each command. Multiple commands can be used. The parameters are placed in a file with a key field. The RTVBIGPARM command is used in batch to retrieve the information.
The Change Bit command allows one or more bits to be changed in a byte to either *ON (‘1’) or *OFF (‘0’). The bits are numbered 1 - 8 with 1 being the high order bit. A variable must be specified for the &RTNBYTE parameter and all BITn parameters cannot be specified as *SAME.
The Change Class 2 command allows a change to one or more *CLS object types. CHGCLS2 simplifies making mass changes to *CLS objects. For a more complete understanding of the parameters, see the CHGCLS command help text. A *CLS object owned by one of the system profiles may not be changed.
The Change Command Library command allows you to change the name of the alternate library used for TAA commands (and a few other TAA objects). Depending on the existing command library, you may be asked to run DLTTAACMD and/or DUPTAACMD.
The Change Cancel Key command works in conjunction with the RTVCNLKEY tool command. CHGCNLKEY allows the setting of the Cancel and Exit key information which may be of value when mixing system and user functions. The QWCCCJOB API is used.
The Change Copyright command changes the language specific Copyright statement in one or all source file members in a library. Only specific source types are supported and considered for changes. If a language specific Copyright statement exists, it is dropped and the new Copyright statement inserted.
The Change Data Base File Date command changes date fields in a file from an MMDDYY, DDMMYY, or YYMMDD format to a different format. This allows rearranging date fields to allow for normal processing based on your typical date format.
The Change Data Base Increments command changes the number of size increments for one or more data base files in a library based on the current percentage of records and a specified new percentage. Only data physical files are processed. The command defaults to ‘check’ meaning no changes occur unless ACTION(*CHANGE) is specified.
The Change DDM File 2 command allows a change to one, generic, or all DDM files in a library. This simplifies making changes when the type of communication has changed (such as SNA to TCP) or other mass changes.
The Change Directory Authorization command changes the authorization to a directory and its objects and all subdirectories and their objects. The command is a front end to the system command CHGAUT and uses the same parameters. CHGDIRAUT simplifies making mass changes to IFS authorizations. You may need to change the test case for your home directory.
The Change Display File 2 command allows a change to one or more display files. Not all of the CHGDSPF parameters are supported. CHGDSPF2 simplifies making mass changes to display files. For a more complete understanding of the parameters, see the CHGDSPF command help text. A display file owned by one of the system profiles may not be changed.
The Change DSPOBJD Outfile Dates command changes all date formats in the outfile created by DSPOBJD that are in an MMDDYY format to either DDMMYY or YYMMDD. The DSPOBJD outfile has several date fields that use the MMDDYY format regardless of the job date format. CHGDSPOBJO makes it easier to work with the dates if you want a format other than MMDDYY.
The Change Distribution List Entry command lets you change or remove an entry from one, generic, or all distribution lists. The From User ID value must match an existing entry. An ACTION parameter exists which defaults to *TEST to allow testing of what the *CHANGE function will provide.
The Change DST Password 2 command resets the DST password to the default value. The purpose of the command is allow a user who is not QSECOFR to reset the DST password. CHGDSTPWD2 may only be used interactively by a user who is authorized to the TAADSTPWD2 authorization list.
The Change Data Queue Description command changes one or more attributes for a data queue. Only standard data queues are supported (not DDM data queues). The API QMHQCDQ is used. Not all attributes are supported by the API.
The Change Data Queue Description 2 command allows a change to one or more *DTAQ object types. Not all of the CHGDTAQD parameters are supported. CHGDTAQD2 simplifies making mass changes to *DTAQ objects. For a more complete understanding of the parameters, see the CHGDTAQD command help text. A *DTAQ object owned by one of the system profiles may not be changed.
The Change Function Name command allows you to change the description of the Function field on WRKACTJOB to provide a better indication of what a job is doing. The command must be used in a CL program and not from a command entry line. The value on WRKACTJOB would appear as USR-xxxx where xxxx is the 10 bytes specified on CHGFUNCNAM.
The Change Generic Objects Owner command changes the ownership of objects with the same generic name. All object types or a list of specific object types may be named. The command simplifies changing ownership of multiple objects. For a single object, the system command CHGOBJOWN should be used. For all library objects, the TAA Tool CHGLIBOWN should be used.
Change Group Profile. Allows a dynamic change of a group profile. The command must be run within the job that is attempting to make the change to another group profile. This is a form of multiple group profiles, but provides support for only a single group profile at a time. There are security considerations in making the change. Useful for dynamically changing the security environment.
The Change Group Profile 2 command allows you to change all members of a group profile for the parameters OWNER, GRPAUT, or GRPAUTTYP. This provides a simple method of ensuring all members of the group have the same attributes related to group profile processing.
The Change IFS Owner command allows a change of ownership of IFS objects. The list of IFS objects to operate on is created as part of the command. The objects for a specific owner or the ownership of all objects found may be changed. An option exists to check what changes would occur.
The Change IFS Owner 2 command changes all IFS objects owned by one user profile to another. This allows a simple means of switching owners. An option exists to revoke the current owners authority. You must have *ALLOBJ special authority to use CHGIFSOWN2.
The Change Initial Menu command checks or changes the initial menu in one, generic, all user profiles, or in the profiles belonging to a group profile. System profiles are never changed. An existing initial menu may be named to ensure that only specific changes are made. The current initial menu value may be a specific initial menu, *ANY, or *SIGNOFF.
The Change Initial Program command checks or changes the initial program in one, generic, all user profiles, or in the profiles belonging to a group profile. System profiles are never changed. An existing initial program may be named to ensure that only specific changes are made. The current initial program value may be a specific initial program, *ANY, or *NONE. If the same library exists twice on the list, only the first occurrence is returned.
The Change Job Description 2 command allows a change to one or more *JOBD object types. Not all of the CHGJOBD parameters are supported. CHGJOBD2 simplifies making mass changes to *JOBD objects. For a more complete understanding of the parameters, see the CHGJOBD command help text. A *JOBD object owned by one of the system profiles may not be changed.
The Change Job Queue Jobs command allows changes to one, generic, or all jobs in a job queue. The jobs may be held, released, or ended. In addition, some parameters from CHGJOB are also valid such as JOBQ, RUNPTY, OUTPTY, OUTQ, etc.
The Change Job Queue 2 command allows a change of one or more *JOBQ object types. CHGJOBQ2 simplifies making mass changes to *JOBQ objects. For a more complete understanding of the parameters, see the CHGJOBQ command help text. A *JOBQ object owned by one of the system profiles may not be changed.
The Change Job’s Spooled Files command changes all the spooled files for a job for specified attributes such as changing to a different form type. This simplifies cleanup at the end of a job for spooled files created during the job.
The Change Library List from Job Description command changes the user portion of the library list to the value in a named Job Description. A value of *SYSVAL is supported in the JOBD and causes the library list to be changed to the value of the QUSRLIBL system value. CHGLBLJOBD can be used to simplify changing the library list in some environments.
The Change Logical File 2 command allows a change of one or more logical files. Not all parameters from CHGLF are supported. CHGLF2 simplifies making mass changes to logical files. For a more complete understanding of the parameters, see the help text for CHGLF. A logical file owned by one of the system profiles may not be changed.
The Change Library Object Authorities command changes the owner, authorization list, and individual authorities of one or more objects in a library based on the output of the CVTLIBOBJA command. This may be used to help keep the authorization information the same between libraries on different systems.
Change Library Owner. Changes the owner of a library and the objects within the library. Only the objects owned by the specified owner are changed. The old owner can remain authorized or be removed. Useful for cleaning up libraries or when distributing libraries to other systems.
The Change Maximum Members command changes the number of maximum members for one or more data base files in a library based on a specified percentage. Only data physical files are processed. The command defaults to ‘check’ meaning no changes occur unless ACTION(*CHANGE) is specified.
Change Message Description 2. If you have second level text that exceeds 512 bytes, the CHGMSGD2 command provides a simple solution for maintenance. The first display shows the current values for all other parameters using the command prompter. Then a special display is shown with 1500 bytes of second level text. A third display is optionally available for an additional 1500 bytes of text.
The Change Message Queue 2 command allows a change to one or more *MSGQ object types. Not all of the CHGMSGQ parameters are supported. CHGMSGQ2 simplifies making mass changes to *MSGQ objects. For a more complete understanding of the parameters, see the CHGMSGQ command help text. A *MSGQ object owned by one of the system profiles may not be changed.
The Change Object command provides either CHGxxx or WRKxxx commands for most object types that can be changed. While the command is intended for use as a menu option where the object and object type are already known, it may be used as a general purpose CHGxxx command. Either a system or TAA command is used.
The Change Object Authority command allows changes to authority for one, generic, or *ALL objects in a library of a specific type, or all types. A list of up to 50 users may be specified for specific authorities or to remove all authorities.
The Change Object Authorization List command changes the authorization list for one, generic, or all objects in a library. The authorization list may also be set to *NONE. This simplifies making mass changes.
The Change Object Authority 2 command changes the *PUBLIC user of an object to the CRTAUT value of the library where the object exists. If the library value is *SYSVAL, the QCRTAUT system value is accessed and used. CHGOBJAUT2 allows existing objects to have their authority changed to adhere to the library default.
Change Object Description 2. Provides a simple interface to the QLICOBJD API. It allows changes to program attributes such as the source file/lib/member used for the create, the user attribute (not the object attribute), PTF and APAR information, etc. You must be authorized to the TAACHGOBJ2 authorization list to use the command. Useful for developers of packages and for some internal control situations.
The Change Object Description 3 command provides an interactive display to allow any object text to be changed. The user must be authorized to change the object. The text is shown as a 50 byte field with a ruler above. This makes it simpler to make changes such as to a specific position in the User Profile Text description as described in the PAGSEP tool.
The Change Object Description 4 command provides a general purpose solution when a program wants to prompt for a CHGxxx command. Only typical object types and attributes are supported. Assuming you have provided a proper interface to CHGOBJD4, the command will complete normally whether the change has been made, the command prompt was cancelled, or the command failed. The ESCMSGID parameter will be blank if a successful change was made.
The Change Object Owner 2 command is similar to the system CHGOBJOWN command except that generically named objects and all object types can be changed with a single command. This simplifies changing ownership of generic objects.
The Change Object Source command provides a simple method of changing the source information in an object to reflect the information from a specified member. The command is intended for the case where an object is created from temporary source and you want the object to reflect the actual source. The user must be authorized to the TAACHGOBJ2 authorization list.
The Change Out Queue 2 command allows a change of one or more *OUTQ object types. Not all keywords used by CHGOUTQ are supported. CHGOUTQ2 simplifies making mass changes to *OUTQ objects. For a more complete understanding of the parameters, see the CHGOUTQ command help text. An *OUTQ object owned by one of the system profiles may not be changed.
Change Owned Objects. This command transfers the ownership of objects from one user to another. No QDOC documents are transferred. There is system support on the DLTUSRPRF command to perform this, but it deletes the named profile. CHGOWNOBJ offers a subset function. A spooled file lists all of the changes.
The Change Owner from Tape command provides a ‘fix up’ of ownership. CHGOWNTAP is designed for the case where object ownership has been changed and you want to reset the ownership to the owner that exists on a save tape. A listing is produced with one line for each object with flags for those objects that were changed or could not be changed. You must be authorized to change ownership of the individual objects.
The Change Physical File 2 command allows changes to one, generic, or all physical files in a library. Only the typical parameters that are changed by CHGPF are supported by CHGPF2. An omit list of files may be specified.
The Change Program 2 command allows a change to one or more *PGM object types. Not all of the CHGPGM parameters are supported. CHGPGM2 simplifies making mass changes to *PGM objects. For a more complete understanding of the parameters, see the CHGPGM2 command help text. A *PGM object owned by one of the system profiles may not be changed.
Change Product Library. Provides a method of placing one or two libraries in the Product Library position of the library list. This can be advantageous when application programs use RPLLIBL to change the library list and you want to ensure that a standard library exists. The QLICHGLL API is used to make the change. The other portions of the library list remain unchanged.
The Change User Profile to *PUBLIC command is designed for the situation where the objects in a library for the *PUBLIC user have different forms of authority and you want to authorize a new user profile to have the same authority as the *PUBLIC user. This would allow you to make the new user profile a group profile for designated profiles and then set the *PUBLIC user to *EXCLUDE to prevent access by non-authorized users.
The Change User Profile to *PUBLIC 2 command is designed for the situation where IFS objects in a directory for the *PUBLIC user have different forms of authority and you want to authorize a new user profile to have the same authority as the *PUBLIC user. This would allow you to make the new user profile a group profile for designated profiles and then set the *PUBLIC user to *EXCLUDE to prevent access by non-authorized users.
Change public authority. Changes the authority for the *PUBLIC user for all or generic objects of all or a specific object type in a library. An option exists to bypass those objects where the public obtains its authorization from an authorization list. Useful for gaining consistent authorization in a library.
The Change Password Attributes command provides separate parameters for each of the QPWDxxx system values. A prompt override program is used to prime the parameter values so that you may key over existing values. You must have *ALLOBJ and *SECADM special authorities to use CHGPWDA.
The Change QDFTJRN Data Area command creates and/or changes the QDFTJRN data area in a named library. The QDFTJRN data area is used by the system to automatically start journaling for objects intended for remote journaling. Using CHGQDFTJRN simplifies entering data into the required data area.
The Change QHST Version command creates a new version of a QHST file. The intent of the tool is to allow you to run the command at the end of some time period where you want to back up complete versions of QHST such as all for the previous month and start a new time period.
The Change RPG /COPY (CHGRPGCPY) command allows changes to /COPY statements in RPG for one, generic, or all members of a source file. The CHGRPGCPY2 exists for RPGLE source which also handles /INCLUDE. The default is OPTION(*CHECK) which means no changes are made and the listing describes what changes would be made. Selection criteria exists for the file, library, or member names in the existing /COPY statement.
The Change Save File 2 command allows a change to one or more save files. Not all of the CHGSAVF parameters are supported. CHGSAVF2 simplifies making mass changes to save files. For a more complete understanding of the parameters, see the CHGSAVF command help text. A save file owned by one of the system profiles may not be changed.
The Change Signon Date command is intended for the case where a user profile swap has occurred and the user profile should be updated so that the current date and time becomes the signon date/time value. CHGSGNDAT may also be used without a profile swap to update the current profile if an option is specified. CHGSGNDAT may only be used in a CL program. The QSYCHGPR API is used.
The Change Signon Error Text tool allows changing of the error message text for the two invalid signon messages. CHGSGNERRT changes the text to a common value. The default text is ‘Invalid signon.’ The RSTSGNERRT command restores the message text to the original values if needed.
The Change Signon Text command allows you to place up to 5 lines of text (79 bytes each) on the Signon Display. The text will appear the next time the Signon display appears. The text does not change if the Signon display is already active. A separate command will allow refreshing the Signon display by subsystem. Both 10 and 128 password Signon displays are supported.
The Change Spooled File Copies command provides a simple change of the number of copies for a spooled file. A prompt override program exists so the user can see the current value before making the change. The intent of the command is to allow a user who should not have full CHGSPLFA function to be able to change the number of copies.
The Change Spooled File Form Type command provides a simple change of the form type for a spooled file. A prompt override program exists so the user can see the current value before making the change. The intent of the command is to allow a user who should not have full CHGSPLFA function to be able to change the form type.
The Change Spooled File Priority command provides a simple change of the output priority for a spooled file. A prompt override program exists so the user can see the current value before making the change. The intent of the command is to allow a user who should not have full CHGSPLFA function to be able to change the output priority.
Change Source Date. Allows changing of the dates kept on individual source statements to appear to be changed on the same date. If a source change takes several days to make, the source statements will have different change dates. CHGSRCDAT allows a range of existing dates to be changed to a consistent date so that it will appear as if all changes occurred on a single date. Useful for documentation.
The Change Source File Length command converts one, generic, or all source files in a library to a source file length that is larger than the current length. The typical conversion is 92 to 112. The same text, owner, and authorities are retained. All existing source members are copied. Conversion to shorter lengths is valid if no data will be truncated.
Change Source Type. Change all or specified source types in a source file to a new type. This avoids having to manually change all of the source types such as RPG38 to RPG.
The Change System Library Text command allows the text descriptions of certain system libraries to be changed to the system supplied value as seen with GO LICPGM. Many system libraries are shipped with blank text descriptions. The default provides a listing of what would be changed. Other library text descriptions such as QDSNX may be optionally changed to English text.
Change TAA Key. Provides a method of changing the critical TAALICENSE data area information. You must enter a special key provided by the TAA Productivity Tools owner to successfully complete the command.
The Change User Auditing 2 command is similar to the system CHGUSRAUD command, but prompts for CHGUSRAUD with the existing values from the user profile. This simplifies making additions or deletions of the AUDLVL parameter which may contain several items.
Change user profile 2. Provides a simple command for Assistant Security Officers who should be limited to the parameters they can change within a user profile. Cannot be used to change sensitive profiles such as QSECOFR. The Security Officer controls the valid parameters by entering them in a data area. CHGUSRPRF2 is an option on the SECOFR2 tool menu.
The Change User Profile 3 command is a front end to the CHGUSRPRF command that allows a list of up to 300 user profile names or generic names to be changed. Most of the parameters from CHGUSRPRF are supported. This simplifies making mass changes to user profiles or for standardizing users of a department.
Change User Password. Allows changing profile passwords or document passwords and replicating the changes on other systems. The password is masked and easily sent using SBMRMTCMD. Unmasking occurs on the other system. Useful for keeping multiple systems in synch with the same passwords.
The Change User Password 3 command allows a command change of a user password that ensures the QPWDxxx system value requirements are met. For example, if you have specified that a required digit exist by use of QPWDRQDDGT. This allows a change to be made by other than the interactive user that still follows your password requirements. CHGUSRPRF can change a password, but does not check the system values.
The Change User Space command allows you to change the contents of a user space. A maximum of 5000 bytes can be changed on a single command. A start position must be named and an optional length.
The Change 128 Password command is intended for those environments using 128 byte passwords where a change to a user password should be replicated on one or more systems.
The Check Active Job command determines whether a job or generic job name is active. This can be helpful in determining if a server job is active. TAA9893 is sent as an escape message if the specified parameters do not find a job.
Check Active Object. Simple technique for determining if an object can be locked to an *EXCL state (is anyone using the object). The command attempts to lock the object and if successful, it unlocks it. Limited to certain object types. Useful for a quick determination if an object is in use.
Check Active Program. Simple technique to include in a CL program to determine if the program is already active. Useful for programs which must run in a single job at a time.
Check Active User. Provides a method of determining if a user is active on the system. Return variables exist for how many interactive and batch jobs are currently in operation for the specified user profile.
The Check Active User 2 command is designed for the situation where you periodically want to check for a list of users to see if they are active. On the first use or when RESET(*YES) is specified, a file is built in QTEMP of the active users. The file is then checked to see if the specified user is active and if not, an escape message is issued. On subsequent uses with RESET(*NO), only the file is checked.
The Check All Data Base File Dependencies command checks all files or all files in all user libraries for the situation where the -Based on- physical file is in a library other than the dependent file. Keeping the -Based on- physicals in the same library is very helpful when attempting to restore on an initialized system or on another system.
Check All Object. Determines if the current user profile (including any Group Profile and Program Adoption) has *ALLOBJ special authority. An escape message (CPF9898) is issued if not. The command is useful in jobs where the user requests to run against all libraries or all user libraries.
The Check *ALLOBJ Owner command checks the owner of an object to ensure he has *ALLOBJ special authority. For example, if a user with *ALLOBJ authority creates a program with USRPRF(*OWNER), but the user is part of a group that does not have *ALLOBJ and the group profile becomes the owner, the program will not run with *ALLOBJ authority. CHKALLOBJO can be used as part of the create step to ensure the proper create of a program.
Check for Apostrophes within a value. The command is used by several TAA tools to ensure double apostrophes and also removes leading or trailing apostrophes. Useful for prompting for a string value (e.g. the TEXT parameter) which needs surrounding apostrophes and may have an embedded apostrophe.
The Check Area Code command provides a method of checking for a valid area code. The TAA9891 escape message is sent if the area code is invalid. An optional completion message is provided. Only the area codes provided by the PRTARACDE tool are supported (includes US, Canada, Caribbean, Samoa, etc).
The Check Area Code Field command checks a named field in a data base file for a valid area code. Depending on the field type, different lengths are valid. Only the area codes provided by the PRTARACDE tool are supported (includes US, Canada, Caribbean, Samoa, etc).
The Check Data Area Spelling command checks for misspelled words in a *CHAR type data area (*DTAARA). The data in the data area would be considered as a string with blanks separating the words. The dictionary supplied by TAA is used by default. Special dictionaries may be named. See the discussion with the TAADCT tool.
Check ASP Objects. The command is intended to assist you in migrating from the old style ASPs (where few object types can exist in an ASP) to the new style. The command finds all of the objects that are in an ASP where the library is not in the same ASP.
The Check ASP Storage command allows you to check a percentage of available storage in an ASP against the size of objects you need to create. An escape message (TAA9896) is sent if the amount of requested storage exceeds a specified percent of available storage. This can be useful when an application needs to duplicate a large object in QTEMP.
The Check ASP (Auxiliary Storage Pool) Threshold tool provides an additional method of notifying the system operator when an ASP has reached its threshold of storage used. A message is sent to QSYSOPR (or a named message queue) that describes the current percentage and remaining storage available. In addition, a separate threshold percentage may be named in conjunction with the SHOUT tool.
The Check *AUDIT Special Authority command checks if the user (including group authority and adopted authority) has *AUDIT special authority. The command completes normally with no feedback if the user has *AUDIT authority. If the user does not have *AUDIT authority, TAA9891 is sent as an escape message.
The Check AUDLOGP command checks audit entries for valid changes to the AUDLOG TAA Tool AUDLOGP file. CHKAUDLOGP helps ensure that the AUDLOGP file is a true representation of the QAUDJRN journal. You must be using the QAUDJRN journal and the AUDLOG tool.
The Check Audit Value command checks a list of specified audit value such as *AUTFAIL against the values in the QAUDLVL and QAUDLVL2 system values. If one of the specified values does not exist, TAA9891 is sent as an escape message.
The Check Bit command checks one or more bits in a byte for an on or off value (‘1’ or ‘0’). The bit positions are labeled 1-8 with 1 being the high order bit. TAA9892 is sent if the bits do not match the requested values.
The Check Blank Fields command checks all values for each field in a file to determine if only blanks exist for character fields or zeros for decimal fields. This is intended as a debugging aid to check if a program that ‘adds new records’ is populating the correct fields. If only some records in the file contain values, the field is flagged with a different code.
The Check Based on File command checks the logical files in a library to determine if they are based on physical files in the same library. A spooled file lists any exceptions. CHKDBD is the companion tool which checks physical files to determine if any dependent logicals exist outside the library. To check all libraries, use the CHKALLDBD tool.
The Check CCSID command checks one, generic, or all objects in a library for a specified CCSID. An escape message (TAA9891) is sent if any exceptions exist and a listing is displayed. Only the object types that support a CCSID are checked.
Check Configuration Change. Checks the configuration objects for those that have changed since a specified date and sends messages for those exceeding the date. This allows a simple review of what has recently changed.
The Check CL Spelling command checks words within quotes in any CL type source. For example, words within parameter values for keywords such as TEXT or MSG can be checked for misspellings. The system Dictionary product is not a requirement as the TAADFT dictionary may be used. A spooled file is created if any spelling errors exist.
The Check Command command provides the functions of QCMDCHK with additional options provided by the QCAPCMD API. This includes 1) Prompting for the command on missing required parameters or some invalid entries and 2) Limited user checking. The command is not run, but can be useful when attempting to simulate a command line on a menu.
The Check Command Default command checks commands in one or more libraries to determine if the system supplied CHGCMDDFT command was used. Some commands cannot be checked and are flagged.
The Check Command Qualified Name command checks the parameters from CRTCMD that support qualified names to ensure that if a program is specified that the library qualifier is not *LIBL. Using *LIBL from a command that is used in a program that adopts authority presents a security exposure where a bogus program could be used.
The Check Command Spelling command checks words within quotes in CMD type source. For example, words within ‘prompt text’ or ‘choice text’ can be checked for misspellings. A spooled file is created if any spelling errors exist. The system Dictionary product is not a requirement as the TAADFT dictionary may be used.
The Check Command Source command checks for whether the source used to create the command objects still exists. ‘Down level’ conditions where the source has been changed after the command was created are flagged. CHKCMDSRC can be helpful in determining if your commands are synchronized between source and object.
The Check CPP Authority command checks command objects in one or more libraries that are specified as *PUBLIC *EXCLUDE. If the Command Processing Program (CPP) is not *PUBLIC *EXCLUDE, the command is flagged. If your intent is to prevent access by the *PUBLIC user to a command, the CPP should also be considered for *PUBLIC *EXCLUDE to prevent the use of the CALL command to the CPP.
The Check CPP use of QSYS command checks all the commands on the system for non-system commands that use a CPP from QSYS. This helps ensure the integrity of your system.
Check Date. Checks a date field to ensure it is valid. Allows for range check and a year check. Useful for date validation.
The CHKDAT2 command provides a method of performing validation against a date field. Not only must the date be valid, but optional parameters allow you to perform some range checking on the value entered. Any system supported date format may be used.
The Check Date 3 tool provides a command to check dates. The major intent of the tool is to call the processing program from a HLL program and pass it an Externally Described Data Structure of information and receive a message back in the Data Structure.
Check Data Base Dependencies. Checks for any physical files in the library you are checking that have dependent logicals in other libraries. CHKBOF is the companion command to check for logical files in the library you are checking that are ‘based on’ a physical in a different library. To check all libraries, use the CHKALLDBD tool.
Check Data Base File. Optional return variables such as Member and library name, source or data file, physical or logical file, number of records and record length. Most of the function can now be achieved more efficiently with the system supported RTVMBRD command.
The Check Data Base File Date command checks one or more date fields in a file for valid dates. A spooled file is created with any errors. The file must be externally described. A variety of date formats can be specified such as MMDDYY, DDMMYYYY, ISO, USA, etc.
The Check Data Base File Member command simplifies checking for a data base file and authority to it. This provides clear messages when the file or member does not exist, the file is not the requested file type, or the user does not have the proper authorization.
Check DDS Spelling. Checks the spelling of DDS literals used in DSPF or PRTF source types in one or all members in a source file. The system Dictionary product is not a requirement as the TAADFT dictionary may be used. Useful for cleaning up code to avoid careless errors that end users love to find.
The Check Decimal command checks a string of up to 512 bytes for whether only digits 0-9 exist. Embedded blanks are considered invalid. A check for a leading and trailing minus sign is optional.
The Check Directory Entry command checks the directory (see WRKDIRE) using the outfile of DSPDIRE to determine if the full user ID (ID, address, and description) exist. If not, TAA9894 is sent as an escape message.
The Check Duplicate Access Path command checks for files in one or more libraries that have a duplicate access path with another file. The system will automatically share an access path if it can. Complete duplicates and partial duplicates (where only the high order keys are the same) are listed. The purpose of CHKDUPAP is to assist in cleaning up objects that are not needed.
The Check for Duplicates in a List command is used to check command parameters that are simple lists to ensure that each entry in the list is unique. Only the first duplicate found is described with the TAA9896
The Check Duplicate Object command checks for duplicate object type/names in multiple libraries. A listing is output describing the duplicate groups. This can be helpful when attempting to clean up the system or solving problems.
The Check Duplicate Spooled File command checks an outfile created by CVTOUTQ for duplicate spooled files. The check is made on the qualified job name, the spooled file name, and spooled file number. CHKDUPSPLF is intended for the case where the system may be creating duplicates.
The Check File Attribute command provides a simple check of an existing file to ensure it has an attribute that you want to process. A list of one or more valid file attributes must be provided. If the attribute of the named file is not in the list, TAA9896 is sent as an escape message.
The Check File Source command checks for whether the source used to create the objects still exists. ‘Down level’ conditions where the source has been changed after the file was created are flagged. CHKFILSRC can be helpful in determining if your files are synchronized between source and object.
The Check Field Spelling command checks the spelling of a field in a data base file. The field must be of a character type and can contain up to 5000 bytes. A spooled file is printed of any misspelled words found. The system Dictionary product is not a requirement as the TAADFT dictionary may be used.
The Check Format command checks for a format and/or level ID in a file. File types that support formats may be specified. A specific format may be named or the special value *FIRST. Different escape messages are sent if the format does not exist or the level ID does not match. No completion message is sent if the command completes normally.
Check Generic. Checks a variable to see if it contains a generic value (e.g. ABC*). Returns the length of the field. Useful when working with generic requests.
The Check Generic Objects command provides a method of checking if any generic objects exist for a specific name. The default is to check for all object types. A return count is optional. TAA9893 is sent if no generic object names exist.
The Check Group Profile command checks a profile to see if it is a group profile. TAA9891 is sent as an escape message if the profile is not a group profile. You must have *USE authority to the group profile to use CHKGRPPRF.
The Check Hex command checks a string of hex characters such as ‘C1C2C3’ to ensure valid hex characters exist. A string of up to 512 characters may be checked. You must use the RTNLOC value to determine if an error exists. CHKHEX can be helpful when a user is entering hex characters which must be validated.
The Check Holiday command allows you to check a list of specific holidays against the current system date so that some CL code may be bypassed or executed. For example, if a backup is not needed on Christmas, you can check and bypass the save. TAA9892 is sent as an escape message if the current date is one of the holidays you specified.
The Check IASP Status command checks that all IASPS are online. An omit list of IASPs may be specified. An escape message (TAA9892) is issued if all requested IASPs are not online.
Check IBM Library. Provides a means in a CL program of determining whether a library name is considered an *IBM or *USER library and whether the library will be saved by a SAVLIB option (e.g. SAVLIB LIB(*ALLUSR)). The command provides a program method of providing the information from the SAVLIB chart in the Backup and Recovery Guide. Useful for automating backup and following the rules of the system function.
Check IBM Profile. Provides a means in a CL program of determining if a user profile is considered a system profile or not. Useful for separating system versus user profiles.
The Check IFS Damage command attempts to save one or more individual IFS objects to a save file. *DIR, *FLR, and *DOC objects are bypassed. Messages are sent for those objects which could not be saved. While this is not a perfect solution, the messages can be used to indicate damage situations.
The Check IFS Entry command checks for object existence and/or verifies the user’s authority to an object in the IFS. If the object exists and the user has the correct authority to the object, the command completes normally. The CHKIFSE command is similar to the system CHKOBJ command, but does not check for program or group adopt (IFS restriction).
The Check IFS Open command provides a method of determining if an IFS object is available for a type of use and allows a specified type of sharing with other jobs. If the open is successful, the file is closed and the command completes normally. If the file cannot be opened, TAA9872 is sent as an escape message.
The Check IFS Save command displays or prints a listing of IFS objects that need to be archived (saved). An outfile is optional. Using WRKLNK and option 8 (Display attributes), you can see the ‘Need to archive (System)’ information for an IFS object. It is changed to ‘Yes’ when the object is saved with a SAV command specifying UPDHST(*YES). CHKIFSSAV allows a review of the objects needed to be saved.
The Check IFS Spelling command checks the spelling of the data in a stream file. The data is converted to the TAA240 source file in QTEMP and the TAA CHKSPELL2 command is used to check the spelling. Error indications appear with sequence numbers as if the data was in a source file. The data is limited to 240 bytes wide for the stream file.
The Check Inactive tool provides a function to end or discontinue inactive interactive jobs. The typical example is where the user has walked away from the workstation without signing off. The system values QINACTITV and QINACTMSGQ are used plus a standard program which runs continuously in batch. A list of exception devices/users may be specified and a list of ‘run status’ values may be used to check whether to perform an action on the job.
The Check Inactive Job 2 tool is a series of commands that allow the ending or discontinuing of jobs that have been inactive for a specified period of time. This allows security control when users walk away from their devices while still signed on. It may also be used to end jobs that are hung. CHKINACT2 allows for different timeout values while the CHKINACT tool has a single timeout value.
Check Job Log Message ID. Provides a program solution for determining if one or more message IDs exist in a job log. This can be useful in determining whether the job log should be printed or deleted.
The Check JOBACGP command checks audit entries for valid changes to the JOBACG TAA Tool JOBACGP file. CHKJOBACGP helps ensure that the JOBACGP file is a true representation of the QACGJRN journal. You must be using the QACGJRN journal and have set auditing for the JOBACGP file.
Check Job Control Authority. Provides a method of determining if a user has *JOBCTL special authority. The checking includes the user, group profile authority, and program adopt. Optional user error text may appear as the escape message.
The Check Job Description library tool checks for a named library in the INLLIBL parameter of one, all, or generic job descriptions. This simplifies hunting for a library name.
Check JOBD USER Parameter. Checks the job descriptions in one or all libraries for those with a specific user named in the USER parameter. Shows the authority to the JOBD object. Useful for security review.
The Check Job End Status command is intended for batch jobs that are waiting for a delay time and periodically need to check if an End Job or End Subsystem command has issued a controlled cancel - OPTION(*CNTRLD). CHKJOBENDS allows a periodic wakeup with a total time specified. The escape message TAA9891 is sent if a controlled cancel has been requested.
The Check Job Function command checks for an active job having a specific Function type-description as seen with WRKACTJOB such as ‘PGM-xxx’. Multiple jobs may satisfy the request. A job name is required. Both the Function type and the Function description are optional.
The Check Job Message Wait command allows you to send a notification when a job is waiting for a response to a message (MSGW status). The notification can be one or more of 1) Send a break message to a message queue on the current system, 2) Send a break message to a workstation on a different system (using FTP), 3) Send an Email to a user (using TAA tool SNDTXTMAIL)
The Check Job Status command provides a simple test to determine if a job exists and what the status is (such as *JOBQ, *ACTIVE, or *OUTQ). A job type such as INT or BCH may also be specified. An exception message is optional if more than one job meets the criteria.
The Check Journal Library command checks a library to see if a specified list of object types is journaled to a named journal. Physical data files, data areas, and data queues may be checked. Diagnostic messages are sent for the objects that are not journaled and a final escape message occurs if any objects are not journaled.
The Check Locked System Value command checks a system value to see if it is locked by the DST/SST function. This prevents certain system values from being used by CHGSYSVAL (or the Change option on WRKSYSVAL). The escape message TAA9896 is sent if the DST/SST function has been used and the system value is one that is on the list that may be locked. Otherwise, the command completes normally.
Check Leap Year. Checks a year to determine if it is a leap year. Passes back a Y/N value. The years 1600 - 4000 are supported.
The Check Library Integrity command checks for integrity of objects in a library. CHKLIBITG is a front end to the system command CHKOBJITG which checks the owned objects of a user profile and creates an outfile of exceptions. The checking ensures such things as whether the object is in the proper domain, a determination of whether a program or module has been tampered with, or whether a CISC program has not yet been converted to RISC.
Check Library list. Provides a method of determining if a library is anywhere on the current jobs library list. An escape message is sent if it is not. Optional return variables exist to assist in determining where the library is on the library list. This includes the system portion, the product portion, the current library, and the user portion. The system allows certain combinations.
Check Library Owner. Checks ownership of all objects in a library for a specified owner. Useful for ensuring consistent ownership in libraries and ensuring user objects are not found in system libraries.
Check User Profiles for Limited Capability *USER types. Provides a method of checking or ensuring that all *USER type profiles are specified as LMTCPB(*YES).
The Check Low Level Message command allows you to monitor for a message ID sent by a command that does not send an escape message. The message being sent must be from a message file (it cannot be an ‘impromptu’ type). See the example in the tool documentation for how to use CHKLVLMSG.
The Check E-Mail Address command checks the validity of an E-Mail address. The local-portion of an address is ensured to have proper syntax. The domain-portion is either syntax checked or checked using APIs to determine if the domain name exists. To check if the domain name actually exists, your system must have access to a domain name server.
The Check E-Mail Field command checks a field in all records in a file for a valid E mail address. A listing is output. The local-portion of an address is ensured to have proper syntax. The domain-portion is either syntax checked or checked using APIs to determine if the domain name exists. To check if the domain name actually exists, your system must have access to a domain name server.
The Check Member Spelling command checks the spelling of the words in the member text for all members in one or more files in a library. Both source and data members are checked. The command defaults to use the dictionary provided by the TAA Productivity Tools. A specific dictionary or multiple dictionaries may be used.
Check Member 2. Similar to CHKOBJ, but sends an escape message if the member does exist. Useful for simplifying coding when it is considered an error if the member exists.
The Check Minimum Release command finds objects that were created with a target release earlier than the one specified on the command and determines if the source still exists. *PGM, *MODULE, and *SRVPGM objects are checked. All *SQLPKG objects are flagged. Objects with creation data may be bypassed. The companion tool to re-create the objects is FIXMINRLS. The tool is designed to assist in conversion to V6R1M0.
The Check Multiple Members command checks one or more files to determine those that have more than one member and those that allow more than one, but have 0 or 1 members. Exceptions are displayed or listed. Source files are implicitly bypassed. Only data base data files that can have members are checked (DDM is excluded).
The Check Message Description Spelling command checks a single message description for the spelling of the first and second level text. CHKMSGDSPE is helpful after adding or changing a message description. To check the spelling of all message descriptions in a file, use CHKMSGSPE.
The Check Message ID command checks if a message ID exists in a message file. The command completes normally if the message ID exists and sends TAA9891 as an escape message if it does not.
The Check Message Spelling command checks the spelling of message descriptions in message files. Both 1st and 2nd level text are checked. A spooled file is created. The system Dictionary product is not a requirement as the TAADFT dictionary may be used.
Check Name. Checks for a valid name. Useful for name validation within a HLL program.
The Check Name Field command allows you to check or update a name and address field in a file for names such ‘THomas ThuMb’ or ‘Thomas thumb’ and have them changed to ‘Thomas Thumb’. The field to be checked is ensured to have the first letter of each word capitalized and the remaining letters to be lower case.
The Check Name Field 2 command allows you to check name and address values for proper case such as ‘THomas ThuMb’ or ‘Thomas thumb’ and returns a value of ‘Thomas Thumb’. The return value is ensured to have the first letter of each word capitalized and the remaining letters to be lower case.
The Check Object All command provides a simple check to see if an object name exists on the system. The library qualifier and the object type default to *ALL. The TAA9893 escape message is sent if the object does not exist.
The Check Object Attribute command checks for an object attribute such as RPG or PF. The value ‘*ALL’ is considered valid. TAA9893 is sent as an escape message for an invalid attribute. The command is useful for checking other command input which allows an object attribute.
Check Object Authority. Is intended for checking the authority to a generic object name or all objects in a library. Useful for allowing a security check before proceeding into an application function.
Check Object Damage. Sanity checks the objects in a library or all libraries for damage. The objects are saved one at a time to a save file in QTEMP. If damage is detected, it is reported. It is still possible for damage to exist and be saved. See the discussion with the tool. See also the VALDBF command for better damage checking of data base files.
The Check Object Spelling command checks the spelling of the words in the object text for one or more objects in a library. The command defaults to provide the dictionary provided by the TAA Productivity Tools. A specific dictionary or multiple dictionaries may be used.
The Check Object Source tool performs 3 functions: 1) Lists objects that were created from source but the source no longer exists where it was created from 2) Lists source members which have not been used to create an object and 3) Lists source members which have been used to create more than a single object. An attempt is made to identify ‘possible’ missing items based on the last source change date and time.
The Check Object Type command checks an ‘Object Type’ value to see if it is valid. Any object type that can be checked by CHKOBJ is considered valid. TAA9896 is sent as an escape message if the object type is not valid.
Check Object 2. Similar to CHKOBJ, but sends an escape message if the object does exist. Useful for simplifying coding when it is considered an error if the object exists.
The Check Object 3 command is like the system CHKOBJ command except that a better first level message (including the type of object) is sent if the object is not found. CHKOBJ sends a CPF9801 message where the first level text reads ‘Object xxxx in library yyy not found’. Typical error text from CHKOBJ3 would be ‘File xxxx in yyy not found’.
The Check Object 4 command is intended to assist you in identifying all the objects of a name or generic name on the library list, in a specific library, all libraries, etc. Messages are returned when an object is found.
The Check Old Objects command prints a list of objects that have not been used since a specified use date. A list of object types may be entered. A list of libraries (including generic) or all user libraries may be specified along with an omit list. An outfile of the old objects is optional.
The Check One Job command determines if there is only a single job at a workstation. The command is intended for those situations where you want to ensure that only a single job is active before performing some task that will not operate correctly if multiple jobs are active. PCs with multiple sessions and non-programmable workstations with ‘jump’ key jobs are not considered.
The Check Owner Change command compares the current owner of one or more objects to the owner that created the object and displays a listing. Those objects with the same owner are bypassed. Options exist to process only those owned by a named user or created by a named user.
The Check Owner of Save File command checks the objects in a save file to see if they are owned by a specified user. If a library object is in the save file, it is also checked. An option exists to check the owner of the save file. TAA9896 is sent as an escape message if a different owner exists.
The Check for Passthru Job command checks the current job to see if it is a passthru job. Escape message TAA9894 is sent if it is not a passthru job. The command has no parameters and may only be used in the interactive environment.
The Check Program Attribute command provides a simple check of an existing program to ensure it has an attribute that you want to process. A list of one or more valid program attributes must be provided. If the attribute of the named program is not in the list, TAA9896 is sent as an escape message.
Check Program OIR. Provides a method of checking a library or libraries to ensure that the system DSPPGMREF command will operate correctly. A list of program objects in the library is accessed and DSPPGMREF is used for each program. Errors are monitored and a report prepared. Useful in identifying specific objects if you have or suspect damage in the OIR (Object Information Repository) of the system which prevents DSPPGMREF from operating correctly.
The Check Program Owner command is intended to be included in programs which must adopt authority (USRPRF = *OWNER). The command allows the program to be checked to ensure that the program still uses adopt and that the owner has the specified required special authorities.
The Check Program Release command allows you to check for programs and modules that were created on a specific release. You may run the command over multiple or all libraries. Options exist to exclude certain releases, omit a list of libraries, and to replace the program or module if the source exists.
Check Program Source. Checks a program or module and its associated source to see if the source still exists and if the program is ‘down level’ from the source. A single library, *USRLIBL, or *ALLUSR libraries may be checked. The source statements are read to determine the date of last change. A replace option is available. Useful for determining if the source still exists for the program and module objects and if it is down level.
Check Program Stack. Allows you to specify a program name and determine whether the same program is already in the program stack. Useful for programs that cannot be called recursively.
The Check Public Authority to Authorization List command checks an authorization list to ensure: 1) the *PUBLIC user is *EXCLUDE and 2) the *PUBLIC authorization to each object controlled by the authorization list matches a command option (the default is *AUTL meaning the *PUBLIC user is controlled by the authorization list). A spooled file is created with the authorization list, the controlled objects and any exceptions.
The Check Password Block command provides the same function as the system V6R1 support to control users who attempt to change their password too frequently. The system supports checking with the use of CHGPWD, but not with CHGUSRPRF. CHKPWDBLK is intended to be placed in a program that uses CHGUSRPRF to change passwords, but also wants to ensure infrequent changes. TAA9897 is sent as an escape message if the time limit has not passed.
The Check Remote Journal command checks for an *ACTIVE journal state of a remote journal. If the state is not *ACTIVE, different escape messages are sent to describe the current state (*INACTIVE = TAA9895, *FAILED = TAA9896, and *CTLINACT = TAA9897). This provides a simple means of testing for the critical ongoing requirement that allows remote journaling to be successful.
Check RPG CALL. Checks an RPG or RPG38 source member and determines if any CALL operation codes exist. If so it sends an escape message. Useful for determining if sub-programs are used so that a source member can be reviewed in more detail to determine what program is called.
The Check RPG command checks for the existence of the CRTRPGPGM command in library QSYS. This is primarily an internal tool to prevent tools from being created by CRTTAATOOL on systems that do not have the RPG compiler. If the CRTRPGPGM command does not exist in QSYS, CPF9801 is sent as an escape message.
Check RPG Spelling. Checks the spelling of RPG literals used in output specifications in one or all members in a source file. The system Dictionary product is not a requirement as the TAADFT dictionary may be used. Useful for cleaning up code to avoid careless errors that end users love to find.
The Check Restricted State Status command sends an escape message if the system is not in the restricted state. The check is against the ‘system state’ and not the status of the controlling subsystem as it is possible for the controlling subsystem to be restricted, but not have the system in the restricted state.
Check Save Strategy. Checks a single library or all libraries and compares the save date/time against the last change date/time for each object and member. A listing is printed of all those objects and members which do not have a current backup. Useful for checking your save strategy to ensure you are properly backed up.
Check Save Device. The command does a sanity check of the Save/Restore device and the system by saving a test data area from TAATOOL and restoring it to QTEMP. The value within the two data areas and some of the object attributes are compared to help ensure that device and system are operating properly. CHKSAVDEV is intended to be included at the beginning of your standard backup programs.
The Check Save File command is designed to allow you to determine if a save file is available for use. For example, if a save is occurring to the save file, TAA9892 will be sent as an escape message.
Check Save/Restore Job Log. Checks a job log for important save/restore messages. Nets out the job log to allow responsible data processing person to review for problems (e.g. damage, object not saved or restored, object changed on restore).
Check *SAVSYS Special Authority. Determines if the current user profile (including any Group Profile and Program Adoption) has the *SAVSYS special authority. An escape message (CPF9898) is issued if not. The command is useful in jobs where the user needs to save or restore and it is not known if he is authorized.
Check Save Tape. Checks a save/restore format tape to see if it can be read by the system. This is a sanity check only and does not ensure that the tape can be properly restored. It does cause all of the data on tape to be read by the system which is a better test than the system command DSPTAP. Checks save/restore tape format which includes any tape media produced by a SAV command, a new release tape, or a PTF tape.
The Check *SECADM Special Authority command determines if the user has the special authority *SECADM. Group profile, supplemental group profiles, and program adoption authority are also considered. The *SECADM special authority is needed for various functions involving user profiles.
The Check Select/Omit command allows select and/or omit lists to be checked against a name value. The lists may contain generic names. A *YES/*NO result field is returned to assist in your processing. CHKSELOMT simplifies programming when performing select/omit processing of names against lists.
The Check Signon Count tool allows you to prevent a signon (interactive job) if the number of current signons for a specific user profile exceeds a maximum. The supplied TAA program must be named in the INLPGM parameter or used in the users initial program. A system default and unique user profile values may be specified.
The Check Special Authorities command allows a check of a specific user’s special authorities or the current user. If the current user is requested 1) the check includes both program adopt and group adopt and 2) the check occurs at the previous call level so that the current program adopt function is not included.
The Check User Space Spelling command checks for misspelled words in the first 32,000 bytes of a user space. The data in the user space would be considered as a string with blanks separating the words. The dictionary supplied by TAA is used by default. Special dictionaries may be named. See the discussion with the TAADCT tool.
Check spelling. Provides a method of spell checking the data in a source member. The system Dictionary product is not a requirement as the TAADFT dictionary may be used. Multiple dictionaries may be named and dictionaries exist in TAATOOL for your use. A data area which names a list of dictionaries may be named (see the CRTDCTARA tool).
Check spelling 2. Provides a method of checking the spelling in a string of data. The system Dictionary product is not a requirement as the TAADFT dictionary may be used. A command exists, but the CPP may also be called directly. If a word is not found in the dictionaries specified, it is returned in a parameter along with the number of the word in the string. Options exist to start the checking after a word.
The Check Spool Control Authority command checks for the special authority *SPLCTL in the current user profile or as an adopted function. If the user does not have the function in his job, the CPF9898 escape message is issued. Standard text describing the error is the default.
The Check Spooled File command checks for the existence of a spooled file and optionally for whether the spooled file is still open. If the job exists, but not the spooled file, TAA9883 is sent as an escape message. If the job does not exist, TAA9884 is sent as an escape message. If the option to check for an open status is used and the file is still open, TAA9885 is sent as an escape message.
Check Source Type. Checks the source types in a source file for valid types. No syntax checking will occur in SEU unless SEU recognizes a valid source type. Options to check for i5/OS, S/38, S/36 or *ALL source types. Useful for ensuring all source types in a source file are valid and of a particular type.
The Check Source Type 2 command provides a simple check of an existing source member to ensure it has a source type that you want to process. A list of one or more valid source types must be provided. If the source type of the named member is not in the list, TAA9896 is sent as an escape message.
The Check Source Type 3 command checks a value to see if it is a valid source type as described by the Programmer Menu. TXT and TXT38 are optional.
The Check Standard Jobs command provides a method of determining if required system and standard processing jobs are active. CHKSTDJOBS operates by using the output of the TAA CVTWRKACT command when the system is known to be in a good state and checking the jobs to see if they are still active.
Check System Condition. Monitors the critical system messages arriving on the QSYSMSG message queue and uses the SHOUT TAA tool to shout at users. Useful for preventing critical system conditions from going unnoticed.
Check S/38 Commands. Checks a set of CL source for commands which are not part of S/38 Release 8. The commands to be checked against are in a table which can be modified. Useful for situations where source must be shipped to another system and you want to determine if any user commands exist. Also can be used for enforcing standards regarding what commands can appear in a CL program.
The Check TAA Authorities command checks the current authorities for TAA objects and compares them to the shipped version of the product. TAA objects in QSYS may also be included in the check such as Authorization Lists. This allows a simple determination of what authority changes have been made on your system. This helps ensure that the TAA Tools may not be used without proper authority.
The Check TAA Authorization Lists command checks to ensure that all TAA Authorization Lists are set to *PUBLIC *EXCLUDE. This is the recommended setting. Allowing *PUBLIC access to many TAA functions such as CPYUSRPRF2 would be considered a security violation in most installations. An option exists to change to *PUBLIC(*EXCLUDE).
The Check TAA Changes command helps provide an understanding of potential incompatibilities when moving to a new update or version of the TAA Productivity Tools. The tool is run automatically at the time of install using the last used date of the previous TAA commands and a listing is output. The information may not be 100% complete, but should provide a review of what you should consider.
The Check TAA Change 2 command checks the last change date of objects in TAATOOL against the date the TAA version was installed. Any objects changed after the install date are listed. This allows a review of what has changed since the TAA Productivity Tools were installed. An *ALLOBJ user is required.
The Check TAA Command checks for TAA commands in a source file or all source files in a library or all libraries. The command is helpful for determining what usage is being made of TAA commands. See also the “Determining TAA Tool usage” topic on HELPTAA.
The Check TAA Create System command provides a check of all objects in TAATOOL to determine if they have been created on a TAASYSnn system. A listing is produced of any exceptions. It is not an error to create your own version of some TAA function, but CHKTAACRT provides an auditor with a tool to review if changes from the shipped version have occurred.
The Check TAA Dependencies tool is intended primarily as an internal tool used when CRTTAATOOL is run. The command checks a list of dependent tools (those that are prerequisites). If a dependent tool does not exist, CPF9898 is sent as an escape message.
Check TAA libraries. Provides a sanity check of the TAA Productivity Tools by ensuring all objects exist and there are no ‘foreign’ objects in the TAA libraries.
The Check TAA License command provides a simple check to see if a valid TAA Productivity Tools license exists. The completion message describes whether a full or demonstration license exists. If a demonstration license exists, the date the license expires is described.
The Check TAA Outfiles command checks for any existing TAA outfile names to determine if the level ID is the same as that used by the current tool. The command is run automatically when the TAA Productivity Tools are installed and may also be run at any time. The output listing describes outfiles that may need to be deleted for successful tool use.
The Check TAA Owner command checks in critical TAA programs that the owner has *ALLOBJ authority and if an *AUTL was used on CRTTAATOOL that it is still assigned to the object.
Check TAA Product. Provides a method of checking for commands on the the system that use the same name as the TAA Tool command names and objects that begin with the generic name TAA that are not part of the TAA Productivity Tools. The output can assist you in cleaning up old version of TAA Tools and avoiding name conflicts.
The Check for TAA Commands in QSYS command checks for TAA command names that have a duplicate name in QSYS. This is intended to assist in identifying if a new system command uses the same name of an existing TAA command.
Check TAA Tool. Provides a problem determination assist by creating a spooled file containing the source members of a tool and the create information. If an object was not created on a TAASYS system, the source create information is also provided.
The Check Tape Ready command is designed to be used when an unattended save is to take place later. The command will ensure that the tapes are ready and are valid to write on. This includes an optional check for Volume ID, expiration date, and the CHKSAVDEV TAA Tool.
The Check Tape 2 command is similar to the system CHKTAP command. Neither the system CHKTAP nor the SAVxxx commands will send an inquiry message to the device’s message queue if the tape is not in a ‘ready’ status (such as no tape is mounted), the volume ID does not exist, the sequence number does not exist, etc. CHKTAP2 sends an inquiry message requesting a C = Cancel, or R = Retry response.
The Check Target Release command checks the programs in a library to determine if they were created for a release that is more current than the minimum release specified on the command. The intent of the tool is to check a library prior to a save where the TGTRLS parameter is to be used.
The Check Time command checks for a valid time in HHMMSS format. The time must be in a range of 000000 to 235959. Valid minutes and seconds are also checked for. If the time is invalid, the CPF9898 escape message is sent.
The Check Time Stamp tool provides a command to check timestamps as defined by the data base type Z fields. The major intent of the tool is to call the processing program from a HLL program and pass it an Externally Described Data Structure of information and receive a message back in the Data Structure.
Check User Authority. Checks user authority excluding program adoption. One command exists for objects and another for authorization lists. Useful for programs that operate under program adopt that need to know if the user is actually authorized to an object without including program adoptions. The function is partially replaced by the CHGPGM USEADPAUT(*NO) function.
The Check User Command checks for user commands in a source file or all source files in a library or all libraries. Both TAA and user commands are identified. The command is helpful for determining what usage is being made of user and TAA commands. See also the “Determining TAA Tool usage” topic on HELPTAA.
The Check User for Group command checks if a user profile is a member of a named group either by the GRPPRF or SUPGRP attributes of the profile. TAA9891 is sent as an escape message if the user profile is not a member of the group. No completion message occurs if the user profile is a member.
The Check User Space command is intended to be used after a list API writes data into a user space. CHKUSRSPC checks the Information Status byte to ensure that the data is completely contained within the user space. This is intended for CL programs that use a list API which may write more than 16 MB of data and is not handled by the program.
The Check Value command is intended for the case where the user inputs a value to a CL program and the value must be validated. CHKVAL offers several checking options that vary depending on the type requested. Special values are also supported. Standard error text may be used to simplify the explanation of any errors.
Check Week. Checks a data area to see if the value is equal or less than the current date. If so, it updates the data area by seven until it is passed the current date and returns a positive indication. Useful for inclusion in initial programs when specific functions should be performed during signon for a particular day of the week (such as SBMJOB).
The Check Word command checks the spelling of a word. An escape message is sent if the word is not in one of the specified TAA dictionaries. The default dictionary includes about 80,000 English words, places, proper names, system words (eg QCLSRC), TAA words (eg ADDDAT), and PRTSEUTXT words (eg PARM1).
The Check 1st Member command checks one or more files to determine if the first member has the same name as the file. Exceptions are displayed or listed. Source files are implicitly bypassed. Only data base data files that can have members are checked (DDM is excluded).
Check i5/OS Commands. Checks CL source for commands which are not part of the current i5/OS release. Commands can be added or subtracted to the checked list. Useful for situations where source must be shipped to another system and you want to determine if any user commands exist or for enforcing standards regarding what commands can appear in a CL program.
The Calculate Boolean Value command provides input of 2 arguments of 4 byte fields and returns the result in either or both a 4 byte character value or an 8 byte hexadecimal value. The operation performed can be *OR, *AND, XOR, *NOR, *NAND, or *NOT. The arguments must be 1-4 byte *CHAR type fields. They may be variables, literals, or hex values.
Calculate Date Differences. Calculates the number of days between a ‘from date’ and a ‘to date’. Useful for determining the number of days between two dates.
The Calculate Date Difference 2 command determines the number of years, months, and days between 2 dates. This calculation is used in the insurance industry. The date formats of the From and To dates may differ in format. The two dates must be valid and the From date must be less than or equal the To date.
The Calculate Date Difference 3 command determines the number of days between 2 dates. The date formats of the From and To dates may differ in format and all date formats are supported. The two dates must be valid and the From date must be less than or equal the To date.
The Calculate Date Difference 4 command is like CLCDATDIF3, but allows a list of one or more day names to be specified. This allows an answer to a question such as ‘How many Tuesdays and Thursdays exist between 2 dates?’
Calculate date/time is designed to be used when you want to use the SBMJOB SCDDATE/SCDTIME parameters to submit a job based on hours or minutes from the current date/time or a specified date/time. CLCDATTIM determines the new date/time and provides return variables.
The Calculate Date/Time 2 command returns the difference in terms of number of minutes (an optionally the number of seconds) between a From date/time and a To date/time. CLCDATTIM2 may be useful when determining time differences.
The Calculate Days command allows you to determine how many specific days (Sundays, Mondays … Saturdays) exist between two dates. You may name one or more days in the week to be considered. For example, you can count the number of Tuesdays and Thursdays that exist between two dates (the start and end dates are included).
The Calculate Data Base File Hash command determines a hash value for the data in a data base member. The intent of the command is to provide a comparison method for large files on different systems without transporting the entire file and making a comparison. An optional outfile HASHP may be written. The CMPDBFHSH command is supported to compare HASHP files in different libraries.
The Calculate Large Variable command allows CL to work with character variables that exceed 15 bytes in length and contain up to 30 digits. Simple operations of Add, Sub, Multiply, and Divide are supported. Any values placed in the Factors are right aligned.
The Calculate Modulus 10 command calculates the value for a Modulus 10 Self-Check Digit. The command returns a value for the self-check digit which is intended to be added to a number such as a customer number. DDS supports the CHECK(M10) keyword for a field to assist in ensuring the number is keyed correctly.
The Calculate Modulus 11 command calculates the value for a Modulus 11 Self-Check Digit. The command returns a value for the self-check digit which is intended to be added to a number such as a customer number. DDS supports the CHECK(M11) keyword for a field to assist in ensuring the number is keyed correctly. Some input values cannot produce a Modulus 11 self-check digit and an escape message will be sent.
The Calculate Square Root command calculates the square root of a numeric value that is greater than 0. The input value should be passed as a *DEC (15 5) value which allows numbers such as 123 or 123.456 to be input. The return value must be specified as *DEC LEN(15 5).
Calculate Time Differences. Calculates the number of seconds between a ‘from time’ and a ‘to time’. Useful for working with those commands which only support a wait of a number of seconds and you want to wait until a specified time.
The Calculate Time Zone Difference command returns the number of minutes difference between two time zones. The time zone names as used by WRKTIMZON must be input or special values such as *PACIFIC. Daylight savings time is considered. An optional return value describes the difference in HH:MM format. A minus value may be returned.
The Calculate UCC Check Digit command calculates the check digit for several UCC standards such as UPC-12 used for most grocery items. This can be used to assist in assigning the value for a new item.
Cleanup System. This command combines the functions of several other TAA tools to provide a simple means of cleaning up the systems. A batch job is submitted. You can optionally allow the following to occur MTNJRN, DLTOLDSPLF, RMVOLDMSG, DLTQHST, and DLTOLDQRPL.
Cleanup TAA Temporary Files. This command should be used to cleanup files that exist in TAATOOL that are used for temporary functions. The command can be run in off hours to reduce the amount of space on the system.
The CLP Data Base Record tool provides a command interface to allow a CL program to position to (key or RR), read sequentially, read randomly (by key or RR), write, update, and delete data base records. A record buffer (string of data) must be provided (the tool does not operate on a list of fields).
CLP Outfile Processing Code. This is documentation only (including sample code) for how to code an outfile in a CL program. The code is ready to be copied in from the SEU browse function by requesting the CLPOUTFILE member in QATTINFO.
CLP Standard Error Handling Code. This is documentation (including sample code) for how to do standard error handling in a CL program. The code is ready to be copied in from the SEU browse function. Two forms of the code are provided. The simple form is designed for typical user applications. The second form is designed for tool use and is the same error handling code as available in the DUPSTDSRC tool (it includes other code).
CLP Subroutine code. This is documentation only (including sample code) for how to code a subroutine in a CL program. The code is ready to be copied in from the SEU browse function by requesting the CLPSUBR member in QATTINFO.
The Clear All Physical File members command clears all members that exist in a physical file. You must have *OBJEXIST rights to the file and at least one member must exist.
Clear Data Area. Provides a method of initializing a data area. *CHAR types are set to blanks. *DEC types are set to zeros. *LGL types are set to ‘0’.
The Clear Data Queue command clears a non-keyed data queue of all entries. A keyed data queue may be cleared of a specific key or all entries. The command uses the API QCLRDTAQ.
The Clear Generic Members command clears one or more generic members in a data base file (either source or data). The system supports a generic capability on RMVM, but not on CLRPFM. CLRGENMBR provides the missing function to allow cleanup of certain files.
The Clear Generic Source command clears generic members in one or more source files in a specified library. Special values such as *STD may be used for the source file name to clear generic members from source files such as QCLSRC and QCMDSRC. The default is ACTION(*CHECK) which describes in messages the members that would be cleared.
The Clear Job Queue 2 command clears selected jobs from a job queue. Jobs may be cleared based on a combination of selection criteria such as job, user, status, and priority. At least one selection type must be made. A job must satisfy all selection types specified to be ended. A ‘check option’ exists to allow a determination of which jobs would be ended.
Clear Logical File Member. Clears a logical file member and the based on physical members in the best performing method. The logical member is added back at the end of the command. Useful for those applications which need to reuse physical members each day and logical files are built over more than a single physical.
The Clear Library 2 command is like the system CLRLIB command, but also clears objects that can cause CLRLIB to fail such as dependent logical files in a different library, constraints specified by ADDPFCST, receivers that have not been saved, and output queues with entries. Some exceptions exist that may prevent a cleared library.
The Clear Message Queue 2 command allows you to clear messages from one or more message queues based on the number of hours a message has been on the queue. CLRMSGQ2 may be used for any system message queue such as QSYSOPR or QSYSMSG or any user message queue. The command defaults to ACTION(*CHECK) to provide an indication of what would happen if ACTION(*REMOVE) had been specified.
The Clear Output Queue 2 command clears all but a specified number of spooled files from an output queue. The spooled files are first sorted in descending sequence by open date/time. The spooled files are then read, the specified number are bypassed, and the remainder are deleted. CLROUTQ2 simplifies keeping an output queue with a manageable number of spooled files.
The Clear Output Queue 3 command clears selected spooled files from an output queue. Spooled files may be deleted based on a combination of selection criteria such as job, user, form type, status, and priority. At least one selection type must be made. A spooled file must satisfy all selection types specified to be deleted. A ‘check option’ exists to allow a determination of which spooled files would be deleted.
The Clear Stream File command clears a stream file in the IFS. The IFS entry will still exist, but the size of the entry will be 0 as seen by the WRKLNK display of attributes for the entry. The TAA RTVIFSED command will also return a 0 value for the size.
The Clear Tape command clears the information about the tape labels on a specified device. This allows new data to be written to the tape. Unlike INZTAP, CLRTAP retains the existing Volume ID and Owner ID. Because it must access existing information, CLRTAP is slower than INZTAP. An option exists on CLRTAP to prompt INZTAP using the current values found on the tape.
The Clear User Index command clears the entries from an existing user index. Any user index may be specified (not just those created by the TAA CRTUSRIDX command).
The Clear User Space command clears a user space by resetting it to the initial value (as specified when the user space was created). The full size of the user (may have increased since the space was created) is reset.
Command Data Queue. Allows commands to be asynchronously executed. The typical use is for users who are capable of using commands, but the function is general purpose and can be used in any application. If you are use to entering commands, the Command Data Queue can make you more efficient.
The system supports the capability (as of V4R5) to retrieve a command that is about to be run or to change a command that is about to be run. This function provides significant capability, but there are important restrictions. This is no guarantee that your exit program will be used for all conditions. This is a ‘documentation only’ tool with sample code on how to do an Exit program for a command.
Command Line. Provides skeleton code for simulating a command line on a system menu or display. The functions of command prompting, F9, message subfile and logging of commands is provided. Sample code describes how to include your own options on the menu. The command is used only for testing purposes.
The Compare All Source command compares one, all, or generic source members in one or more source files in a library to the same file and members in a different library. A listing is produced for each file and the members. If the corresponding member does not exist or the data does not match, the member is flagged. An option exists for a detail comparison of unmatched members.
The Compare Authorization List Authority command compares the authorizations from one *AUTL object to another. This includes the owner and individual authorities. Differences are noted including From *AUTL users who do not exist for the To *AUTL and vice versa.
The Compare Class command compares the CRTCLS command parameters of two Class objects. A spooled file is created of any differences.
The Compare Command command compares the CRTCMD command parameters of two command definition objects. A spooled file is created of any differences.
The Compare Command List command is intended for the case where a command supports both an ‘include’ and an ‘exclude’ list of system names or generic system names. CMPCMDLST ensures that both lists are unique and generic names do not overlap specific names (or generic names) in the other list. TAA9896 is sent as an escape message for non-unique situations. An option exists to allow generic overlap.
The Compare Command Parameters command compares the parameter lists of the command source against the source for the CPP. A single command, a generic command name, or all commands in a library may be compared. The CPP must be written in CL or RPG.
Compare Date. Compares two dates. Provides optional return values for the result (GT LT EQ) and the number of days between. Useful for working with date comparisons.
The Compare Date 2 command provides a simple comparison of a specified date to the current date plus or minus a number of days. A return variable that will contain GE or LT must be specified. The command is very efficient if the dates to be compared are in the current year. CMPDAT2 provides a simple method of determining whether a date is in a range of days from the current date.
Compare Data Base file. Compares two data base file members (up to 9999 record length). Options exist to print in character or hex and to compare a range of positions. Differences are noted with asterisks. Useful for comparing output that should be identical.
The Compare Data Base Formats command compares the format information between two data base files. If the formats differ, a detail comparison of each field occurs. This can be helpful when you have created a program using one file and execute against a different file that is supposed to be identical and a level check occurs.
The Compare Data Base File 2 command compares two identical format unique keyed files and lists the changes to the data for a specific field name. CMPDBF2 allows you to make a periodic copy of a uniquely keyed file and then compare the current version against the last copied version to see the changes for a specific field.
The Compare Data Base File 3 command compares a member from two data physical files. The files are copied to temporary files in QTEMP and a logical file is built over each file with the key as the entire record. The From file is then read and an attempt is made to to randomly access the same key in the To file. Exceptions are noted. The process then repeats for the To file.
The Compare Display File Description command compares the CRTDSPF command parameters of two Display file objects. A spooled file is created of any differences.
The Compare Data Area command compares the contents of two data areas. The attributes of the data area (type, length, and decimal positions) must match in order to compare the values. The TAA9895 escape message is sent if the values do not compare. From and To positions may be compared for character data areas.
The Compare Data Area Description command compares the CRTDTAARA command parameters of two data area objects. A spooled file is created of any differences.
The Compare Data Queue Description command compares the CRTDTAQ command parameters of two Data Queue objects. The contents of the data queues are not compared. A spooled file is created of any differences.
The Compare Data Queue Entries command compares the entries and keys (if any) for two data queues. The intent of the command is to allow a comparison when data queue entries are duplicated such as in a remote journal environment. The date/time values of when an entry was sent are not compared.
The Compare Environment Variables command allows a comparison of environment variables between two systems or two versions converted from the same system. A listing is printed noting the differences between the two ENVVAR files being compared.
The Compare IFS command is designed to assist when you want to ensure that IFS objects in one or more directories on different systems or partitions are the same. The CAPIFS command must be used on both systems/partitions to capture the IFS information. The two libraries containing the CAPIFS information must exist on the same system when CMPIFS run. A spooled file is displayed or output with the differences.
The Compare IFS Entry Description command compares the major attributes of two IFS objects. A listing is produced if any differences exist. An escape message is issued if differences exist and the command is run in batch or OUTPUT(*PRINT) is specified.
The Compare Job Attributes command compares the attributes of two jobs. A display or listing is output of any differences found. When two jobs differ in how they operate, CMPJOBA may be helpful in identifying why they differ.
The Compare Job Description command compares the CRTJOBD command parameters of two Job Description objects. A spooled file is created of any differences.
The Compare Job Queue Attributes command compares the CRTJOBQ command parameters of two Job Queue objects. A spooled file is created of any differences.
The Compare Job Schedule Entries command may be used to compare the values of job schedule entries from two different systems or from a previously captured version from the same system. The CVTJOBSCDE TAA command must be used to capture the information.
The Compare Journal Attributes command compares the CRTJRN command parameters of two Journal objects. A spooled file is created of any differences.
The Compare Journal Image 2 command provides a significantly better approach to comparing journal images than the system CMPJRNIMG command. Instead of comparing record images and packed data, CMPJRNIMG2 provides field names and converted values. A selected set of field names may be named or all fields in the record. CMPJRNIMG2 allows comparisons to be made when only after images exist (2 images must exist for the same relative record number).
The Compare Journal Information command is intended for comparing journal attribute information from different systems. Both journal and attached journal receiver attributes are compared. The CVTJRNINF command (part of this tool) must be used to capture the information in an outfile. After placing two outfiles from different systems on the same system, CMPJRNINF may be used to make a comparison.
The Compare Journal Receiver Attributes command compares the CRTJRNRCV command parameters of two Journal Receiver objects. A spooled file is created of any differences.
The Compare Logical File Description command compares the CRTLF command parameters of two Logical file objects. A spooled file is created of any differences.
The Compare Library command compares the contents of two libraries for the same objects, same size, same type, etc. Options exist to compare the physical file data (both source and non-source).
The Compare Library Authority command compares the Create Authority for a library to the objects within the library. If the authority of the *PUBLIC user differs from the library Create Authority, the object is listed. Libraries with an Authorization List used for the Create Authority are not supported.
The Compare Library Description command compares the CRTLIB command parameters of two Library objects. A spooled file is created of any differences.
The Compare Library Format command compares one or more physical files in one library to the same file names in another library. The comparison is done for the number of fields, the record length, and the level ID. This can assist in ensuring files that are intended to match have the same format in different libraries.
The Compare Library Object Authorities command compares the output of two uses of CVTLIBOBJA and prints a list of differences. This may be used to compare the authorizations between what should be the same library on different systems or a previous version of the authorizations from the same library.
The Compare Library 2 command is designed to assist when you want to ensure that one or more libraries on different systems or partitions are the same. The CAPLIB2 command must be used on both systems/partitions to capture object and member information. The libraries containing the CAPLIB2 information must exist on the same system when CMPLIB2 run. A spooled file is displayed or output with the differences.
The Compare List Parameters command allows the comparisons of list values passed to a CL program from a command that uses two lists. The intent of the tool is to be used when a command being checked in a CPP supports a list of items to include and a list of items to omit. An error occurs if both lists contain the same value.
The Compare Level ID command compares level IDs for one, generic, or *ALL files in one library to another. An escape message is optional if differences exist. CMPLVLID may be helpful for situations such as when a file in a production library must match the same file in the test library.
The Compare Member Description command compares attributes of one, generic, or all members (either data or source) in two different files. Only the member text, number of records, number of deleted records, and ‘share’ attribute are compared. Unmatched member names in the To file are flagged. Unmatched member names in the From file may be optionally flagged. CMPMBRD may be helpful when ensuring member attributes are identical in two files.
The Compare Menu command compares the CRTMNU command parameter values of two Menu objects. A spooled file is created of any differences.
The Compare Module Attributes command compares the attributes of two module (*MODULE) objects. A spooled file is created of any differences.
The Compare Message Descriptions command compares message descriptions in one message file to another. Corresponding message IDs are checked for in both files and the individual attributes of a message description are compared for matching IDs. A range of message IDs may be specified. A spooled file is created with any differences.
The Compare Message File Attributes command compares the attributes of two Message File objects. A spooled file is created of any differences.
The Compare Message Queue command compares the message text of messages in two different message queues. The first 256 bytes of each message is compared and any differences are flagged. If you are using message queues for an application where the messages are data rather than text, CMPMSGQ may be helpful when a duplicate message queue is required.
The Compare Message Queue Attributes command compares the attributes of two Message Queue objects. A spooled file is created of any differences.
The Compare Network Attributes command compares two different uses of CVTNETA and describes any differences. Each use of CVTNETA creates a named member with one record containing unique fields for all of the network attributes. The value of each network attribute is compared between the two file/members by CMPNETA. CHGNETA of MAXINTSSN to bump it by one, do the compare, and then reset MAXINTSSN.
The Compare Object Security command compares security from one object to another. Individual authorities, ownership, and authorization lists are compared. If both objects are *PGM types, the USRPRF attribute and the USEADPAUT attribute (set by CHGPGM) are also compared.
The Compare Object Security 2 command allows a comparison of one, generic, or all objects in a library to a specific object. This allows a determination if all security is being handled identically for a set of objects. A summary spooled file is output with one line for each object checked. Detail spooled files will exist for each object where the security differs.
The Compare System Outfiles command compares the formats used by system outfile commands from the current release to a previous release. For example, you may be interested to know if the DSPOBJD outfile format has changed in this release. A display or a listing is produced. The QA* files in QSYS used for outfile formats are compared.
The Compare Output Queue command compares the major attribute information from each spooled file in one or more output queues to the same information created on another system. The CAPOUTQ command must be used on both systems/partitions to create a library with the spooled file information. The two created libraries must exist on the same system when CMPOUTQ run. A spooled file is displayed or output with the differences.
The Compare Output Queue Attributes command compares the CRTOUTQ command parameters of two Output Queue objects. A spooled file is created of any differences.
The Compare Physical File Description command compares the CRTPF command parameters of two Physical file objects. A spooled file is created of any differences.
The Compare Program command compares the various Create xxx program and CHGPGM command parameters of two program objects. A spooled file is created of any differences.
The Compare Program Parameter command checks the parameter lists between a calling and called programs. Only CL and RPG types are supported. A single program, generic programs, or all programs in a library may be checked. A summary listing highlights any exceptions and a spooled file exists for each call where the parameter lists differ.
The Compare Printer File Description command compares the CRTPRTF command parameters of two Printer file objects. A spooled file is created of any differences.
The Compare Registration Information command compares two different uses of the CVTREGINF command and describes any differences. Each use of CVTREGINF creates a named member with one record for each combination of exit point and exit program. The values of each combination are compared from the two file/members by CMPREGINF. This will add an exit program and remove it when complete.
The Compare System Reply List Entries command compares two versions of the RPYLSTP file output by CVTRPYLE. This may be used to compare against a previous version on the same system or to compare against the output from two different systems.
The Compare Subsystem Description command compares the attributes and entries of two subsystem descriptions. A spooled file is output with the results.
The Compare Signon to Last Used command allows a check to see if a profile is being used after the last signon date. This could occur if the profile name has not signed on since it was used such as in a SBMJOB command or a job schedule job. User profiles that are not permitted to signon will normally appear.
The Compare Spooled Files command allows the comparison of two spooled files. An option exists to bypass certain lines such as heading lines where a date or time may have changed. A spooled file is output with the differences highlighted.
The Compare Spooled File Attributes command compares many of the spooled file attributes between two spooled files. A display or listing is output of any differences found. When two spooled files differ in how the output occurs, CMPSPLFA may be helpful in identifying the differences.
Compare Source. Allows the comparison of two source members and prints the differences between the members. Only the differences are printed with an indication of whether the statement has been Added, Changed, or Deleted. The old version of the tool has been renamed to CMPSRC3.
The Compare Source Parameters command compares the parameter lists between two source members. The command is intended to assist in determining that the parameter lists are identical between the From and To source members. CMD, CL, and RPG source types are supported.
Compare Source Members 2. Simple comparison of two source members or all source members in a file. If two members are compared, an escape message is sent if any differences exist. The message includes the number of statements that differ and the first statement that differs. If all members are compared in one file versus another, a printed listing occurs with one line per member and a summary of the differences found.
Compare Source 3. This is the old version of the command. Compares two source file members and prints a listing of all of the differences. Added or deleted statements are noted as well as identifying the specific changes in some cases. Useful for determining what change were actually made and also for a security audit to ensure that valid changes are being made to critical programs (e.g. Payroll).
The Compare Source 4 command is a front end to CMPSRC2. CMPSRC2 compares one, generic, or all members in a source file to another source file. CMPSRC4 allows all source files (or standard source files) to be compared from one library to another library.
The Compare Stream File command compares two stream files and lists the From and To records that differ. The named stream files are copied to 9999 byte files in QTEMP and compared. If differences are found, the data from each record is listed up to 100 positions.
The Compare Start Up Program command compares the source between the program identified for the QSTRUPPGM system value and the QSTRUP program supplied by the system in QSYS. This can help identify changes that have occurred after installing a new release.
The Compare System Information tool supports several commands to compare different versions of the information in the library specified on CRTSYSINF as captured by the CAPSYSINF command. This allows a determination of what objects are new, have been deleted, or have grown in size more than a specified value. The commands CMPSYSINFO, CMPSYSINFM, and CMPSYSINFI are provided.
The Compare System Objects tool is designed to assist in in determining potential problems when dealing with multiple systems. Because naming conflicts between objects may arise when using multiple systems, the CMPSYSOBJ tool may be used to assist in determining the conflicts within the QSYS library.
The Compare System Values command allows a comparison of system values between two systems or two versions converted from the same system. The CVTSYSVAL TAA command must be used to capture the information on each system in an outfile. CMPSYSVAL then compares the information from the two files and prints a listing noting any differences.
The Compare User Profile command compares the CRTUSRPRF command parameters of two user profile objects. A spooled file is created of any differences.
The Compare User Profile 2 command compares the information between single or multiple user profiles on the current system to the same user profile information from a different system or a different version on the current system. The DSPUSRPRF outfile function must be used to capture the information to be compared.
The Compare User Space command allows a comparison of two user spaces. The first position where a difference occurs causes the command to end with an error message. A start position may be named. Different length user spaces may be compared, but the difference in lengths is noted.
The Compare User Space Attributes command compares the attributes of of two User Space objects. A spooled file is created of any differences.
The Compare Wild Card command provides a comparison of a system name against a compare value that contains fixed and/or floating wild cards. The companion command is CHKWLDCRD which is intended to be used before performing a function such as a DSPxxx OUTFILE or when using a list type API. Additional commands CMPWLDCRD2 and CHKWLDCRD2 may be used on any string (up to 500 bytes) such as customer names or addresses.
The Confirm Delete Data Area command provides a confirmation display and allows F6 to delete the data area. The attributes of the data area are shown along with the Both *CHAR and *DEC (up to 15 digits) data areas are supported. The QWCRDTAA API is used.
Confirm Delete Object. Provides a front end to most DLT commands. A display appears with information from DSPOBJD including the text description, size, and last use date. The operator is given a choice of confirming the delete or cancelling the request. Useful for ensuring you are deleting the intended object.
The Confirm Delete Record command allows deleting a record by entering a relative record number of a record in a file. A prompt appears with the data from the file (characters below X’40 appear as blanks). You must confirm the deletion by pressing F6. CNFDLTRCD may only be used in an interactive environment.
Confirm Remove Member. Provides a front end to the RMVM command. A display appears with information about the member such as the text description, number of records, the last change date, etc. The first 5 records in the member are also displayed. The operator is given the choice of confirming the removal of the member or cancelling the request. Useful for ensuring that you are really removing the intended member.
Constant array. A set of commands that allow you to create a constant array with an optional alternating value that can be accessed with a RTV command in a CL program. Useful for short lists of items that need to be checked or accessed in a CL program.
The Compress Data Base File command compresses a single member, generic members, all members of a data base file or a save file into an output file. CPRDBF is intended for the case where you are transmitting data to another system. The amount of reduced space is very data dependent, but is generally better than the SAV command DTACPR(*YES) function. The companion command is DCPDBF to de-compress the data back to its original form.
The Compress Deleted Records command moves all active records to the front of a data base file member by re-using the deleted record space. At the end of the command, all the deleted records will be at the back end of the file. The companion tool is TRNDLTRCD to move the ‘end of data’ marker after the last active record and reclaim space for the system.
The CPU Monitor tool monitors for jobs that consume CPU resources above a specified CPU percentage. When a job is found running above the CPU limit, a message alert is sent to the specified message queue describing the job which is using too much processing time. If several jobs are found to be over the limit, multiple messages will be sent to the message queue - one for each detected job.
The Copy AFP Resources to Stream File command copies an AFP resource such as a page segment to a stream file. This allows a PC editor such as InfoPrint Designer to edit the information. The stream file would then be copied back and a command such as CRTPAGSEG to be run to re-create the original object.
The Copy Back Data Queue command is intended for refreshing a data queue or duplicating the entries to a different data queue. You must first convert the entries in the data queue to the DTAQP file with the TAA CVTDTAQ command. CPYBCKDTAQ then reads the data from the DTAQP file and uses the QSNDDTAQ API to send the entries to a named data queue. Both keyed and non-keyed data queues are supported.
Copy Changed Members. Copies changed members based on a specified date/time. Allows copies of source to occur for backup purposes even though the file is open for update. Also useful for copying changed members for distribution. For example, if you distribute changes periodically, CPYCHGMBR provides a simple method of copying all of the members that have changed after a specified date/time.
Copy CL. Performs a function similar to RPG /COPY for CL programs to copy in standard source. The support differs in that the CPYCL command must be used to ‘include’ the source. If the program is created and the standard source has been changed, the CRTCPYCL program can be used on an entire library. It will find the programs that need to be refreshed by CPYCL and re-create the programs. Useful for including standard source in CL programs.
The CPYCMD command is designed for Command definition source and allows you to copy in source from another member. CPYCMD acts somewhat as an ‘include’ or the RPG /COPY statement. It provides a solution for having standard source that will change and must appear in several source members.
The Copy CVTOUTQ command provides a copy with selection of the outfile (OUTQP) created by the CVTOUTQ command. CVTOUTQ creates one record per spooled file with the attributes of each spooled file for all spooled files in an output queue. If an output queue contains a large number of spooled files, CPYCVTOUTQ can be used to create a subset to allow simpler processing.
The Copy Data Base Date command copies records in a data base file based on a comparison of a field value and a specified date and operator. Different date formats are valid for character, zoned, packed, date, or time stamp fields.
The Copy Data Base File to Data Queue command copies a member of a data base file to a data queue. The data queue must be non-keyed and have a length less than or equal to 5000 bytes. The QSNDDTAQ API is used.
The Copy Data Base Source command copies PF and LF source types (plus PF38 and LF38) from one source file to another. A generic member name may be specified. The system CPYSRCF command does not allow a copy by source type.
The Copy Directory Entry command retrieves information about the From User ID from the Directory Entries (as seen with WRKDIRE) and prompts for a new entry using ADDDIRE. The existing values for the From User ID are used as the defaults for ADDDIRE with the exceptions of the USRID, USER, and SYSNAME parameters.
The Copy Data Area Command copies the contents of one data area to another. Options exist to create the data area or map from different attributes.
The Copy Data Queue command copies the entries from one data queue to another. Both non-keyed and keyed data queues are supported, but must be of the same type, must have the same key length, and the same sender ID attribute. The entries may be added to or replace the entries in the To data queue. The QSNDDTAQ API is used.
The Copy File With Omit command copies from one file/member to another and omits records with specified values in a designated character field. The To file/member (it may be created) must have 0 records and have the same definition as the From file. The From file/member must not have 0 records. Up to 150 values may be specified to be omitted.
The Copy From Comma Delimited File tool provides two commands to copy comma delimited files (such as from a spread sheet) to an externally described file. CPYFRMCSV should be used for one time functions or for the first time to help you create a customized externally described file. CPYFRMCSV2 should be used when an externally described file already exists.
The Copy From Output Queue command provides a method of storing spooled files in a data base file so they can be printed later. The type of spooled output that can be copied is limited to normal DP type of output (e.g. no graphics) and some spooled attributes are not converted. See the comments in the restriction section. Also see CVTFRMOUTQ which uses APIs and has no restrictions.
Copy from Save File. This command and the companion command CPYTOSAVF allow a save file to be copied to a normal data base file for data interchange purposes. The data base file must be a physical data file with a record length of 528 bytes. CPYTOSAVF can be used on a different system and then a normal restore command. Useful for copying data when a S/370 network is used.
The Copy From Stream File 2 command is a front end to the system CPYFRMSTMF command. CPYFRMSTM2 uses a normal object prompt for a file and member to allow a simple copy from an IFS stream file to a data base member or save file. Only a member of a program described physical file, a member of a source physical file, or a save file may be copied to.
Copy Generic Source. Copies all members with the same generic name. A single source file, standard source files (QCLSRC …) or the TAATOOL source file names (QATTCL …) may be specified. The FROM and TO source files may differ in type. Useful for copying source when a set of different source types with the same generic name must be copied.
The Copy IFS to Spooled File (CPYIFSSPLF) command creates a spooled file from the output of CPYSPLFIFS STMFTYPE(*SYS). The intent of the two commands is to allow a spooled file on a source system to be converted to the IFS, sent as an attachment to an E-mail, received on a target system, downloaded to the IFS, and then converted to a spooled file.
Copy Job Log. Copies the job log from the current or named job to a source member. Only the request messages are copied. Useful for taking commands that were entered interactively and placing them in a source member to achieve a ‘leg up’ on creating a CL program. Useful with OPNQRYF or any time a complex interactive command or series of commands needs to be placed in a CL program.
The Copy Job Schedule Entry command allows you to make a copy of an existing job schedule entry to add a new job schedule entry. A new text description may be assigned. Any other values to be changed must be changed by the CHGJOBSCDE command (such as from the WRKJOBSCDE display).
Copy Many Source File Members. Copies many source file members to a different file. The command allows a list of members with abbreviation types (e.g. *CLP). Each member is copied using CPYSRCF. Useful for copying multiple source members involving different files.
The Copy Message command copies one or more messages with a specific message ID from one external message queue to another. The message is copied to the To queue by the use of SNDPGMMSG. A selection by job, user, and job number may also be made.
The Copy Message Queue command copies messages from one message queue to another. Only *COMP, *DIAG, and *INFO message types are copied.
The Copy New Source Member command copies new members from one source file to another. A specific member, a generic member, or all members may be specified. If the member in the From file does not exist in the To file, it is copied to the To file. If it exists, it is flagged. A listing always occurs.
The Copy Non Generic command copies records from one file/member to another and bypasses the records containing a list of generic values for a named field. This allows ‘all but generic xxx’ to be copied. Most queries do not support a selection by ‘*NE a generic value’. Using CPYNONGEN allows a subset file to be created which can then be queried.
The Copy Null Fields command copies data from a file that contains null fields to a corresponding file that does not have null fields. The null values are changed to zeros. You may create the corresponding file or replace the data in the file if it already exists. CPYNULLFLD may be used to allow functions that do not operate on null field files to be used.
The Copy Program Message Queue Message command copies one or more messages from the current job’s program message queue to an external message queue. You must use RTVMSGKEY to mark the boundary of where messages should begin to be sent from. CPYPGMQM may be used in special debugging situations or on a normal basis to capture problem determination information instead of the entire job log.
The Copy and Reformat command provides better reformatting capability than the system CPYF command which supports only *MAP and *DROP. In addition to *MAP and *DROP functions, CPYRFMT allows renaming of a field. The To file must exist.
The Copy RPG Array command allows the replacement of RPG array data in a source member. It is designed for the case where array data must exist at compile time and a standard procedure is used to create the program. The array data does not have to be the last set of values in the source. A ‘compare value’ must be specified.
The Copy and Shift Left command copies a member beginning at a specified position to another member. This allows shifting of the data to the left. The user must have *ALL authority to the To file to use CPYSHFLFT.
The Copy Shift Spooled File command allows you to shift the data in a spooled file either left or right and re-prints the spooled file. The file must be capable of being copied by CPYSPLF (this excludes files with graphic characters).
The Copy User Space to Data Base File command copies data from a user space to a data base file. The data base file may be up to 9999 bytes in length. An optional parameter allows copying of less than the full space. If the last data in the space is not the full length of a record, blanks will be appended.
The Copy Spooled File Data command reads a spooled file and outputs a file intended for a spread sheet processor. Selection criteria exist so that only columnar data may be output. An option exists to include delimiters and column headings. Either a data base file or an IFS object may be output.
The Copy Spooled File to IFS command copies a spooled file to the IFS as a stream file. The default is to convert the spooled data to a plain text format. Options exist to convert to a rich text format, an HTML format, or a PDF. This allows further use of spooled data to be handled by PC or Internet applications. An option exists to convert to a format that can be re-converted to spooled file on another system.
The Copy Spooled File 2 command is like the system CPYSPLF command except that it adds blank lines and a new page indication to the data base file. If you are going to transfer print lines to some other medium, CPYSPLF2 may be helpful.
The Copy Spooled File 3 command splits a spooled file into multiple spooled files based on a change in value of the data at a specific line and position of each page. Assume you have a report by salesman for all salesmen and want to split the report so there is separate spooled file for each salesman. The salesman number must be listed at the same location on each page, but does not have to be on the first line.
The Copy Spooled File 4 command splits a spooled file into multiple spooled files based on the number of pages specified. For example you may have a report with 100 pages and you want to split into 10 spooled files of 10 pages each, or you may have a 20 page report and you want a separate spooled file for each page.
Copy Spool Text. Allows a spool file to be copied to a source member. Unlike CPYSPLF, CPYSPLTXT provides blank source lines to simulate spacing. An option allows the invoking of SEU to modify the data and reprint the file. Useful for documentation needs when display output is needed in text documents.
The Copy Source Files to IFS tool is meant to provide an easy way to populate an IFS directory from the source physical files in a given library.
Copy source file 2. The command is similar to the system CPYSRCF command. The major difference is that a corresponding member in the To file is first copied to an Old Version file. This allows a backup of what is being replaced or a swap. A single member, generic members or all members in the From file may be specified.
The Copy Source Header command copies a standard source header (several lines of comments) for the heading section of a new or existing source member. Some of the values in the header are updated by the command. The intent of the command is that the programmer would begin a new member by using CPYSRCHDR. Standard PDM options exist. A method of tailoring the standard headers is provided for.
Copy Source Type. The command copies one or more specified source types from one source file to another. A generic member name may be requested. An option exists to remove the ‘copied from’ members.
The Compare System Information tool supports several commands to compare different versions of the information in the library specified on CRTSYSINF as captured by the CAPSYSINF command. This allows a determination of what objects are new, have been deleted, or have grown in size more than a specified value. The commands CPYSYSINFO, CPYSYSINFM, and CPYSYSINFI are provided.
The Copy TAA DDS command is primarily an internal tool used by CRTxxx commands such as CRTSRCCTL. It allows the create to occur using the default of SRCLIB(*TAAARC) regardless of whether a full or demonstration license exists.
Copy TAA Tool. Copies the source members of a specific TAA tool to a different library. Useful for modifying the code associated with a specific tool. The new library must contain the QATT source files (e.g. QATTCL and QATTDDS).
The Copy to CSV command copies from an externally described data base file to a stream file and adds delimiters. The intent is to make a stream file for a spread sheet processor. Options exist to add delimiters at the end of fields, surround fields with quotes, and to include column headings.
The Copy to Flat File command copies an externally described file to a flat file (a single field file). Decimal and binary fields are converted to character and an extra position is added for the sign value for all decimal fields. The flat file must not exist and is created by the command with a length large enough to hold the data. CPYTOFLAT can make a human readable data base file.
The Copy To Stream File 2 command is a front end to the system CPYTOSTMF command. CPYTOSTMF2 uses a normal object prompt for a file and member. The TOSTMF name defaults to allow a simple copy from a data base member to an IFS stream file in the user’s home directory. Only a member of a program described physical file, a member of a source physical file, or a save file may be copied.
The Copy Unique Key Records command copies unmatched keyed records from one file to another. Both files must be keyed and have the same definition. This allows a merging to occur for unique keys. By default, PROCESS(*CHK) is used to check what the results would be. An optional listing of the matched and unmatched records may be specified.
Copy User Profile. Allows a new profile to be created based on an existing profile. The message queue, password and document password parameters are defaulted. The text parameter is specified on CPYUSRPRF. Useful for creating new profiles. The system supported function for copying user profiles is allowed in an interactive mode only. CPYUSRPRF can also be used to capture the CRTUSRPRF command generated and send it to a second system.
The Copy User Profile 2 command is an option on the SECOFR2 menu to allow a user (such as an Assistant Security Officer) to create a new profile by copying an existing profile. The user must be authorized to the TAACPYUSR2 authorization list.
The Copy User Profile 3 command assists in duplicating a user profile from one system to another. The DSPUSRPRF OUTFILE function must be used to capture the information from one or more profiles on the source system. The outfile must then be transferred to a target system. The CPYUSRPRF3 command may then be used to create a new profile based on the existing information.
The Copy User Space command copies the contents of one user space to another. An option exists to control the result if different length user spaces exist. By default, the user spaces must have the same internal length.
The Copy with Deleted Records command provides a simple front end to CPYF when a copy which includes the deleted records of the From File is needed. Options for the beginning and ending relative record numbers are provided. The command may be useful when working with or testing applications that use relative record numbers.
The Create All Proxy command checks for or re-creates commands as a proxy type that have the same name as a command in either QSYS or TAATOOL. Normal user commands are bypassed. Using proxy commands is safer for growth and should be used rather than duplicating a command object.
The Create Bound CL Program 2 command combines the functions of CRTCLMOD and CRTPGM and changes the defaults of certain parameters. The intent is to have a simple create command for single module programs that replaces CRTBNDCL.
The Create Bound RPG Program 2 command combines the functions of CRTRPGMOD and CRTPGM and changes the defaults of certain parameters. The intent is to have a simple create command for single module programs that replaces CRTBNDRPG.
The Create CLP Call Parameters command creates the CALL and DCL statements for a CLP source member using the entry parameter list from a program (CLP, RPG, or single module RPGLE/CLLE). After ensuring a CL source member exists, CRTCLPCALL may be used to add records for the CALL and DCL statements. This simplifies building the proper interface between a CL program and the program to be called.
The Create CLP DCL command creates CLP DCL statements based on the field definitions of an externally described data base file. The DCL statements are added to the end of an existing source member. The statements can then be moved by a source editor to the DCL section of the source. CRTCLPDCL may be useful when dealing with an external definition of a data base file or a data area.
The Create CLP Entry Parameters command creates the PGM and DCL statements for a CLP source member using the call and parameter list from a program (CLP, RPG, or single module RPGLE/CLLE) or from the keywords of a command. After adding a CL source member, CRTCLPENT may be used to add records for the PGM and DCL statements. This simplifies building the proper interface between a program or command which invokes a CL program.
The Create CLP Extract command creates CLP source for use in extracting data from a record buffer to variables declared from a data base file format. The CRTCLPDCL command may be used to create the DCL commands. CRTCLPEXT simplifies the use of a RDDBR command from the CLPDBR tool. See also the CRTCLPINS command which performs the inverse function.
The Create CLP Insert command creates CL source for use in inserting data from variables declared from a data base file into a record buffer. The CRTCLPDCL command may be used to create the DCL commands. CRTCLPINS simplifies the use of an UPDDBR or WRTDBR command from the CLPDBR tool. See also the CRTCLPEXT command which performs the inverse function.
Create command help. A command definition object is named along with a panel group source member. Base help text is created for the command and each of the command parameters. This eliminates most of the need to understand any of the UIM coding necessary to create command help text.
The Create Data Base file with Journal Fields command allows you to create an externally described file that contains the standard journaling fields (such as the user, date, RR number) and the field names from a file that is being journaled. The new form of the command uses the DSPJRN outfile to output records to the file. PRTDB (simple listing of named fields) or PRTDBS (allows select/sort also) could be used to process the entries.
Create Dictionary Data Area. Provides a method of creating a data area in the TAADCT library where a list of dictionaries may be named. EDTCONARR should be used to enter the dictionary names. The dictionaries are intended for use with the CHKSPELL, CHKSPELL2, CHKRPGSPE, and CHKDDSSPE tools. A discussion of the dictionaries provided by the TAA Tools is also included.
The Create Duplicate Data Queue command creates a duplicate data queue (the system command CRTDUPOBJ does not). Only the the parameters for a standard type (non-DDM) data queue are duplicated.
The Create Duplicate Object 2 command is similar to the system CRTDUPOBJ command, but will automatically delete the same object name/type in the To library if it exists. The same ownership or a new owner may be named. This allows a refresh to occur of a subset or duplicate library.
The Create Duplicate Physical file command duplicates a physical file object. The intent of the command is to avoid two problems when attempting to duplicate a model file: 1) CRTDUPOBJ requires *OBJMGT authority which can be undesirable to add to an object for general use and 2) CPYF cannot be used to duplicate a file description unless a member exists. CRTDUPPF allows you to create a file object without a member and allow duplication.
The Create Externally Described Printer File command reads an RPG source member with a program described printer file and creates the DDS for an externally described printer file and the printer file. Exceptions such as duplicate output lines for the same EXCPT line are noted and a new format name is assigned. You must make changes to the RPG source as well as correct any exceptions that are noted.
The Create Generic Objects command allows you to create a number of generic objects with consecutive names like ABC002, ABC003, etc of any object type. The first object must exist in the library where the duplicates will be created.
Create Grace Key. Intended for situations where a temporary software key is needed to the TAA Productivity Tools, but the TAA Productivity Tools owner cannot be contacted for a temporary license. For example, in a disaster recovery situation, the TAA Productivity Tools may be temporarily needed on a system that does not have a valid license. The grace period will last 7 days.
The Create Initialized Record command creates one initialized record from an existing file into a new file. When using the DFT DDS keyword on many physical file fields, you may want to ensure the defaults are set correctly. CRTINZRCD creates an all default record to allow a review. The PRTDB2 command can be helpful in reviewing the values in the new file.
Create logical file source provides for a simple logical file to be created by using only a command interface. A list of key fields may be provided. The DDS is generated and the logical file is created by the command.
The Create List command is intended for the case where a CL program wants to create a variable that can be used to simulate a list passed from a command. This can be used with the TAA EXTLST function.
The Create MI Program command creates a program from MI source. This provides a simpler interface than the QPRCRTPG API.
Create Print Program. Creates a generalized print program for an externally described file that can be used by the PRTDBF command which is part of this tool. PRTDBF is useful for debugging, problem determination, small simple listings, and working with OPNQRYF. It uses the field names as column headings and supports simple listing options of control breaks, left to right field ordering, editing of decimal fields and adding of numeric fields.
The Create RPG Call Parameters command creates the CALL and PARM statements for an RPG or RPGLE source member using the entry parameter list from a program (CLP, RPG, or a single module RPGLE/CLLE). After ensuring an RPG source member exists, CRTRPGCALL may be used to add records for the CALL and PARM statements. This simplifies building the proper interface between an RPG program and the program to be called.
The Create RPG Entry Parameters command creates the *ENTRY PLIST and PARM statements for an RPG or RPGLE source member. The information is extracted from a CALL and parameter list from a program (CLP, RPG, or single module RPGLE/CLLE) or from the keywords of a command. After adding an RPG source member, CRTRPGENT may be used to add records for the *ENTRY PLIST and PARM statements.
The Create Retrieve DCLs command creates DCL commands in a CLP source member for a named RTV command. Rather than keying the DCLs manually, CRTRTVDCL may be used to generate all the DCLs for a retrieve command that allows return variables. The source member must exist.
The Create Subfile Program command creates a file maintenance program which uses a subfile. A keyed file must be specified. Simple validity checking, lower case, and edit codes may be specified. Both display file and RPG program source are generated and then the objects are created. You may need to modify the code to provide for such things as advanced validity checking.
The Create Subfile Program 2 command creates a display file and program (RPG or RPGLE) which allows a display of data from arrays. A ‘position to’ function is optional. It is expected that you will make modifications to the program to build your own array, detail display, etc.
The Create Source File List command creates a data area intended to contain your standard source file names for processing by different TAA Tools. Rather than processing all source files in a library, you can use a specified subset list. After creating the data area, use the TAA command EDTCONARR to enter a list of your standard source files. Three different data areas can be defined.
The Create Standard Source Files command creates standard source files such as QCLSRC in a specified library. This simplifies creating a new library for programmer use. The files created and the assigned source lengths may be specified in a Constant Array.
The Create TAA Proxy Command command should be used when a TAA command needs to be duplicated to a user library. A proxy command uses the command version in TAATOOL. This allows one set of authorizations to exist and prevents errors caused by typical changes to a TAA command in a future TAA version.
Create TAA Source Files. The command creates the standard TAA source files (QATTxxx) in a specified library. This is useful when you want to change a tool. See the discussion for CRTTAASRCF.
Create TAA Tool. Creates a specific TAA tool. Since object is now shipped, the only purpose of CRTTAATOOL is for re-creation of a tool if modifications are needed. See the HELPTAA menu discussion of “Modifying a tool”.
The Create Target Release command assists in creating or changing objects to be saved for a named release. A specific or generic object is named or all objects in a library. Either a new library must be named and must not exist (it is created by CRTTGTRLS) or the objects in the same library will be created for the named release. The TAA Tool RPLOBJ is used to recreate program and module objects and produces a listing of the results.
The Create Test Data command either adds new test data records to an existing member or updates existing records. A prompt appears with the fields from the file and various options may be selected such as consecutive numbers, random numbers, unique numbers, constants, character data, or digit data. Fields not specified are added as blanks or zeros or not changed during an update.
The Create Test Journal command is designed for writing or setting up test cases involving journaling. A journal receiver (TSTRCV0001) and journal (TSTJRN) are created in a named library. You may optionally start physical file journaling and access path journaling to all files in the library. The companion command is DLTTSTJRN.
The Create User Index command creates a user index (*USRIDX) object. Only a fixed length keyed user index may be created. The length of an index entry may be from 1 to 2000 bytes. The user index may be used by other TAA tools or system functions.
Create User Space. Provides a command interface for the API program of QUSCRTUS. Useful if the create function can be done in CL rather than in a call from a HLL.
The Create Virtual Tape tool provides a simple interface for creating, displaying, and deleting a virtual tape structure. The intent of the CRTVTP tool is that you would create or replace a virtual tape structure each time you need to use a virtual tape function and replace or delete it after the tape media is written.
The Create QADBXREF logical file program creates a logical file in QTEMP over the system QADBXREF file. The system QADBXREF file is very complex and cannot be read by OPM programs. Using the file in an ILE program is not easy either. By calling the TAADBINC supplied program, a LF is created in QTEMP that can be used to read the basic fields in the QADBXREF file.
The Convert Access Path command produces an outfile of physical and logical files which have a 4 GB max access path limit. The outfile can be checked for files which are approaching their 4 GB limit. Use of this tool could prevent applications to fail if the 4 GB limit is surpassed.
The Convert Active Profile List command builds an outfile of the user profiles displayed by the DSPACTPRFL command. DSPACTPRFL lists the profiles which will not be disabled by the system ANZACTPRF function. CHGACTPRFL is used to maintain the list. CHGUSRPRF may still be used to disable such a profile. The outfile is named ACTPRFP. The model file is TAASEHSP with a format name of ACTPRFLR.
The Convert All Data Base Dependencies command finds all files on the system or all files in all user libraries for the situation where the -Based on- physical file is in a library other than the dependent file. An outfile ALLDBDP is created containing one record for each dependent file that is in a different library.
The Convert All Group Profiles command builds a keyed data base file with one record for each combination of user profile and group profile. Supplemental groups are considered. The GRPPRFP file is output. You must have *ALLOBJ special authority to use CVTALLGRPP.
Convert All JOBQs. Converts the WRKJOBQ JOBQ(*ALL) listing to a data base file. Release dependent function. Useful for determining the job queues that have pending jobs.
Convert All OUTQs. Converts the WRKOUTQ OUTQ(*ALL) listing to a data base file. Release dependent function. Useful for determining the output queues that have spooled files.
The Convert All Special Authorities command creates an outfile of all special authorities for one or more users. By default, multiple records are written for each user profile: one record for the user, one for his group profile (if any), one for each supplementary group (if any), and a summary record combining all special authority information.
The Convert ARP (Address Resolution Protocol) Table command creates an outfile of ARP table information for a specified line description. Address Resolution Protocol allows physically distinct networks to appear as if they were a single, logical network. The QtocLstPhyIfsARPTbl API is used. The outfile name is ARPTBLP. The model file is TAATCPKP with a format name of ARPTBLR.
The Convert ASP Attributes command builds an outfile of one or all ASPs (Auxiliary Storage Pools). The outfile created is named ASPP. The outfile may then be queried for consistency or searching for specific values such as the overflow recovery policy.
The Convert Audit Journal Entries command converts specific audit entries from the QAUDJRN journal to an outfile. The format of the outfile is determined by the entry type using system supplied model files. The intent of CVTAUDJRNE is to simplify the process of creating an outfile that can be used to write a query against audit entries.
The Convert Audit Log 3 command is designed to convert the Audit Log entries as they are written to the Audit journal in a continuous operation. The command should be submitted to batch, but remains active and acts like an interactive job. A delay time parameter exists to provide for a periodic wakeup of the function. CVTAUDLOG3 is an alternate conversion method instead of the CVTAUDLOG command which is part of the AUDLOG tool.
The Convert Authorization List to Outfile command converts individual authorities for one, generic, or all authorization lists to an outfile. This allows various processing or queries against the information. The outfile is always AUTLP which uses a model file named QAOBJAUT and a format name of QSYDSAUT.
The Convert Authorization List Objects command converts information about library objects, IFS objects, and or *DLS objects for one or more Authorization Lists to an outfile. Each object is represented by one record which includes the full path name. Library objects are also described with their library names.
The Convert Binary to Decimal command exists to allow for compatibility with an old version in QUSRTOOL. The function is no longer needed because CL supports the %BIN function.
The Convert Binary 4 to Decimal command exists to allow for compatibility with an old version in QUSRTOOL. The function is no longer needed because CL supports the %BIN function.
The Convert Binary 8 command allows conversion of an 8 byte character input field (containing a binary value) to a 20 byte character return variable. This allows for conversion of large binary values. Most HLLs allow only for 2 or 4 byte binary values. Only positive values are returned.
The Convert Bits to Byte command converts 8 one byte values (‘0’ or ‘1’) to a single byte. The command is useful if you need to generate a byte with meaningful codes that are made up of bit settings.
Convert Byte to Bits. Converts a one byte value to 8 different return variables which will contain a value of 0 or 1. Useful when dealing with a character value made up of different bit settings.
The Convert Certificates command produces an outfile of information from server or certificate authority certificates on your system. Most notably, certificate expiration dates are output, giving administrators an easy way of checking which certificates need to be renewed before they expire.
Convert Configuration Status. Converts the WRKCFGSTS command to a data base file. Release dependent function.
The Convert Character to Decimal command converts a character field to a decimal value and allows for editing and validity checking options. The command is similar to CHGVAR, but provides for options to simplify CL program coding. CPF9898 is sent as an escape message on any invalid data.
The Convert CLP Command command converts CL commands from CL type source to an outfile. One record would be written for each command with the identifying information such as member name, sequence number, and last change date. Some commands such as SBMJOB or IF which contain a sub command will also cause a record to be written which is identified as a sub command.
The Convert Class Attributes command builds an outfile of one or more Class objects. The outfile created is named CLSP. The outfile may then be queried for consistency or searching for specific values such as those Class objects containing a certain run priority.
The Convert Command Attributes command builds an outfile of one or more Command objects. The outfile created is named CMDP. The outfile may then be queried for consistency or searching for specific values such as those Command objects containing a prompt override program.
Convert Command Keywords. Provides a method of obtaining a data base file of command and keyword combinations from the commands found in a library. One record is output for each combination of command and keyword. Allows several functions to occur when you need to know the existing keywords being used.
The Convert Command Usage command converts the spooled output from PRTCMDUSG to an outfile. This allows you to process all program names that use a specific command. Only a single command may be specified. The outfile is named CMDUSGP and may exist in any library.
The Convert Controller Description ASYNC command converts one, generic, or all ASYNC controller descriptions to an outfile. This provides a simple method of processing the information. The outfile name is always CTLASCP. The model file is TAACFGVP with a format name of CTLASCR.
The Convert Controller Description Host command converts one, generic, or all Host controller descriptions to an outfile. This provides a simple method of processing the information. The outfile name is always CTLHOSTP. The model file is TAACFGYP with a format name of CTLHOSTR.
The Convert Controller Description Local Workstation command converts one, generic, or all local workstation controller descriptions to an outfile. This provides a simple method of processing the information. The outfile name is always CTLLWSP. The model file is TAACFGWP with a format name of CTLLWSR.
The Convert Controller Description Network command converts one, generic, or all network controller descriptions to an outfile. This provides a simple method of processing the information. The outfile name is always CTLNETP. The model file is TAACFGXP with a format name of CTLNETR.
The Convert Controller Description Virtual Workstation command converts one, generic, or all virtual workstation controller descriptions to an outfile. This provides a simple method of processing the information. The outfile name is always CTLVWSP. The model file is TAACFGZP with a format name of CTLVWSR.
Convert Date. Provides a HLL CALL interface to the i5/OS provided CVTDAT command.
The Convert Date 13 command converts the 13 character date retrieved by many system commands in the format CYYMMDDHHMMSS and returns date and time values ready for printing. The date is returned in job format with the job date separator used. The time is returned with the job time separator used.
The Convert Date 2 command is similar to the system CVTDAT command, but supports a wider range of dates. The system command is limited to dates of 1940 to 2039 or 1928 to 2071 depending on the formats. The CVTDAT2 command has a range of years from 1600 to 4000. All of the date formats supported by CVTDAT are available on CVTDAT2.
Convert Day N. Allows a simple command prompt for those cases where the end user must key in a date in the future that is normally thought of as N days from today. The end user keys a date or special values *DAY1, *DAY2 … *DAY60 and an actual date is returned. Useful for scheduling functions or expiration dates.
The Convert Days command converts a range of dates to an outfile. The BUSCAL tool must first be used to a build a Business Calendar (a *USRSPC object) with the years that you want to consider. Days such as Sunday, New Years, Christmas, and specific dates may be excluded. CVTDAYS is then used to build an outfile of dates that have not been excluded.
Convert Data Base File Format. Used for conversion from one file to another when the formats differ and CPYF cannot be used. For example, CVTDBFFMT will allow the conversion from character to decimal or vice versa and allows date formats such as MMDDYY to be converted to a different format such as CYYMMDD or YYYYMMDD. Can be useful when changing date formats to allow for the 21st century.
Convert DDS Source. Converts DDS source from the S/38 environment syntax to the i5/OS environment syntax. Some restrictions exist. Useful for converting to the i5/OS environment.
The Convert Decimal to Binary command exists to allow for compatibility with an old version in QUSRTOOL. The function is no longer needed because CL supports the %BIN function.
The Convert Decimal to Binary 4 command exists to allow for compatibility with an old version in QUSRTOOL. The function is no longer needed because CL supports the %BIN function.
The Convert Device Display command creates an outfile of one, generic, or all display devices. The outfile created is named DEVDSPP. The information in the outfile is taken from the device description for each device.
The Convert Device Printer command creates an outfile of one, generic, or all printer devices. The outfile created is named DEVPRTP. The information in the outfile is taken from the device description for each device.
The Convert Distance command allows a conversion from one type of value such as meters to a different type such as miles. The input value may be up to 9 digits with 2 decimals. The output value may be any of 15/0, 15/2, or 15/5. Conversions can be made for millimeters, centimeters, meters, kilometers, inches, feet, yards, miles, cable lengths, fathoms, and furlongs.
The Convert Deleted Space command converts member information from one or more files to an outfile. It is intended to be used for queries regarding members with deleted record space. If variable length fields exist, the allocated length is output in addition to the maximum record length. A ‘minimum’ amount of total deleted space is included. An omit list of libraries may also be specified.
The Convert WRKDSKSTS command converts the information displayed by WRKDSKSTS and creates a data base file DSKSTSP with one record per disk unit. This allows you to program the information that is on the WRKDSKSTS display. The QYASPOL API is used.
Convert Display Data. When data is sent to a display, care must be taken to not send display control characters. When dealing with packed or hex data, errors can occur if the data is sent to the display. The CVTDSPDTA command converts the data so that it will contain only displayable characters.
Convert DSPTAP Labels. Converts the DSPTAP listing to a data base file. Release dependent function. Useful for automating functions where the information about the labels is needed in a program.
The Convert Data Area command converts the attributes and the data from one or more data areas to the outfile DTAARAV. Both *DEC and *CHAR data areas are supported. The outfile may then be queried for consistency or searching for specific values.
The Convert Data Area Attributes command builds an outfile of one or more Data Area objects. The outfile created is named DTAARAP. The outfile may then be queried for consistency or searching for specific values such as those Data Area objects containing decimal values.
The Convert Data Queue command converts the entries from a keyed or non-keyed TYPE(*STD) data queue to an outfile named DTAQP. One record is written for each entry. The size of the entry field in the outfile is limited to 9,000 bytes. Data is truncated if it exceeds this amount.
The Convert Data Queue Attributes command builds an outfile of one or more Data Queue objects. The outfile created is named DTAQP. The outfile may then be queried for consistency or searching for specific values such as those Data Queue objects with keyed sequence.
The Convert DTS command converts the internal format for date/time known as *DTS into CYYMMDD and HHMMSS return values. The *DTS format appears in various places such as in message data and API formats. A CVTTODTS command is also provided. The QWCCVTDT API is used.
The Convert Edit Descriptions command converts the Edit Descriptions (5-9) to a data base file. This can be used to allow the Edit Descriptions to be transported to another system and entered using the RPLEDTD tool. All Edit Descriptions are output by CVTEDTD. RPLEDTD allows replacing one or all.
The Convert Environment Variables command converts job and system environment variables to an outfile. The outfile can be used to verify current environment variable settings, or to compare ENVVAR settings overtime to ensure they remain consistent on the system.
The Convert File Description command is similar to the system DSPFD command, but only creates an outfile (does not print or display). In addition to the base functions of DSPFD, CVTFD also provides for IASP support. Selection can be made by type of library and a omit list of libraries may be specified.
The Convert Format tool creates an outfile of the formats for a specified file, generic files, or all files in a library. One record per format is output. The API QUSLRCD is used.
Convert From Hex. Converts from a 2 byte hex value (e.g. F0) to a one byte value. Up to 256 characters can be converted to a 128 byte return variable. Useful for conversion work.
The Convert From Output Queue command converts all the spooled files in a named output queue to a named data base file in a library. The companion command is CVTTOOUTQ to convert from a data base file to spooled files. Spool APIs are used so there are no restrictions on the the type of data or attributes that can be converted.
The Convert From Spooled File tool supports both the CVTFRMSPLF and CVTTOSPLF commands. CVTFRMSPLF converts a spooled file to a member in a data base file. Spool APIs are used so there are no restrictions on the the type of data or attributes that can be converted. CVTTOSPLF converts a member back to a spooled file.
The Convert Group Profiles command creates an outfile of the members of a group profile. The user profile information will appear in the outfile if the user profile is specified as the value for the GRPPRF parameter or is in the list supplied for the SUPGRPPRF parameters. This provides a simple method of reviewing and processing the members of a group. The outfile name is GRPPRFP.
Convert to Hex. Converts a value to hex. Useful for conversion to printed or displayed values or when working with packed keys and the OVRDBF POSITION parameter. Also may be used from a HLL by invoking the command processing routine.
Convert Hex to Decimal. Allows a method of converting a hex value to the decimal equivalent in a CL program. Useful for working with Hex values.
The Convert Hex Object Type command converts the internal object type form in hexadecimal (such as 0201) into the external object type form (such as *PGM). For the inverse function, see CVTOBJTYP. For a work display that allows interactive conversion, see DSPHEXOBJ.
The Convert IFS command converts directory entry attribute information from the IFS and outputs the information to a data base file named IFSDIRP. The file can then be processed by other TAA Tools (such as DSPIFS or WRKIFS) or user written programs to extract desired information.
The Convert IFS Authority command converts the authorities of one or more IFS objects to an outfile. One record is output for each user authorized to an object. The command is helpful in building a file that can be analyzed.
The Convert IFS Authority 2 command converts IFS authorities for a single user to an outfile named IFSAUT2P. This allows simplified processing of user authorities. The model file is TAAIFTWP with a format name of IFSAUT2PR.
The Convert IFS Data Authority command converts the output of the RTVIFSEAUT or CVTIFSEAUT commands individual fields to the description for data authorities that is seen using WRKLNK (option 9 for Work with Authorities). For example, if Read and Execute are the only individual data authorities that are specified, *RX would be returned.
The Convert IFS entry authority command converts detail authority information of a single IFS object to a data base file named IFSEAUTP. The file can then be processed by user written programs to extract desired information. See the CVTIFSAUT command for converting authorities for more than a single object.
The Convert IFS Owner command builds an outfile of the owned objects in the IFS (does not include objects in libraries). The system DSPUSRPRF OUTFILE function does not output this information. The QSYLOBJA API is used to extract the information. The outfile is named IFSOWNP and is placed in a specified library. The model file is TAAIFTP with a format name of IFSOWNR.
The Convert Image Catalog command converts the image catalogs to the IMGCLGP outfile in a named library. The QVOIRCLG API is used to retrieve the entries. The model outfile is TAACLGBP with a format name of IMGCLGR.
The Convert Image Catalog Entries command converts the entries for a specific Virtual Tape image catalog to the IMGCLGEP outfile in a named library. The QVOIRCLD API is used to retrieve the entries. The model outfile is TAACLGAP with a format name of IMGCLGER. See the CVTIMGCLG2 command for converting an Optical Image Catalog.
The Convert Image Catalog 2 command converts the image catalog entries for an Optical image catalog to a data base file. The output file is always IMGCLGDP with a model file named TAACLGDP and a format name IMGCLGE2.
The Convert IP Address command checks an Internet Address for a valid format. TAA9892 is sent if the address is not in the correct format. If a ‘generic like’ IP address is entered, a low and high range of addresses are returned. If a ‘generic like’ IP address is not entered, a full address is returned. The intent of the command is to return values that can be easily processed by a program.
The Convert IP Device command converts the IP devices to the IPDEVP outfile in a named library. TCP must be active. Only TCP/IPv4 network interfaces are supported. One record is written for each IP device. The API QtocLstNetIfc is used. For a description of the field values in the outfile, refer to the API documentation for format NIFC0100.
The Convert IPv6 Device command converts the IP version 6 device information to the IP6DEVP outfile in a named library. TCP must be active. Only TCP/IPv6 network interfaces are supported. One record is written for each IP device. The API QtocLstNetIfc is used. For a description of the field values in the outfile, refer to the API documentation for format NIFC0200.
The Convert Job to Outfile command converts the information for one or more jobs to an outfile. Selection may occur on the job or user name as well as the status (*ALL, *ACTIVE, *JOBQ, *OUTQ). The outfile name is JOBP which uses the model file TAAJOFKP and a format name of JOBRCD.
The Convert Job Accounting 3 command is designed to convert the job accounting and/or the print accounting entries as they are written to the job accounting journal. The command should be submitted to batch, but remains active and acts like an interactive job. A delay time parameter exists to provide for a periodic wakeup of the function. CVTJOBACG3 is an alternate conversion method instead of CVTJOBACG or CVTPRTACG.
The Convert Job Description command builds an outfile of one or more Job Descriptions. The outfile created is named JOBDP. The outfile may then be queried for consistency or searching for specific values such as those job descriptions containing a certain job queue.
The Convert Job Locks command converts the locks for a specific job to an outfile. The file can then be processed for a variety of needs. The name of the output file is JOBLCKP. The model file is TAAJOEDP with a format name of JOBLCKR.
The Convert Job Log command converts a job log to an outfile. The system DSPJOBLOG command provides a similar function, but is limited to operating on the current job and produces an outfile with variable length fields. CVTJOBLOG works on any job log and produces a file that can be read by a normal RPG program.
The Convert Job Log 2 command creates an outfile of one record per batch job that was submitted and has completed. Selection on the completion code (defaults to abnormal job end) may be specified. The command is a slow runner, but the outfile can be used to help understand the failures that have occurred. The command is English language dependent.
The Convert Job Performance command converts job performance information for specified active jobs to an outfile. A reset capability exists. This provides a simple summary of such things as CPU seconds used, the percentage of CPU seconds used, transaction count, and response time. The model file is TAAJOFDP with a format name of JOBPERFR.
The Convert Job Queue command uses a system API to access the information similar to WRKJOBQ and creates the data base file JOBQP with one record per job on the job queue. Useful for automating functions for the jobs that exist on job queues.
The Convert Job Queue Attributes command builds an outfile of one or more Job Queue objects. The outfile created is named JOBQAP. The outfile may then be queried for consistency or searching for specific values such as those job queue objects containing jobs.
The Convert Job Schedule Entries command converts the job schedule entries to the JOBSCDP outfile. A specific job name, a generic job name, or all job names may be converted. The data may then be processed as a normal data base file. For example, the file may be saved and restored to another system where the entries could be added by the ADDJOBSCD2 TAA Tool command.
The Convert Job Spooled Files command converts existing spooled files for a specified job to an outfile. The WRKSPLFP data base file is written with one record for each spooled file. This is the same format as used by CVTWRKSPLF. CVTJOBSPLF provides a performance advantage over CVTWRKSPLF when the spooled files for a specific job are needed.
Convert Journal Attributes. Converts the journal environment (i.e. what files and access paths are being journaled), for a named journal to data base files (separate files for physicals being journaled, access path journaling and the receivers). Allows the current journal environment to be saved with the files that are being journaled. The companion command, RSMJRN restarts the journal environment.
The Convert Journaled Data Base Files command converts the physical files that are being journaled to a specific journal to an outfile (CVTJRNP) in a specific library). Each data base record contains the name and library of the file being journaled. Other tools such as RTVPFJRNA may be used to retrieve the journal attributes of a specific file. A Journal API is used internally to access the journaled files.
The Convert Journal Objects command converts the objects that are being journaled from a specified journal to an outfile. Different object types are handled including IFS objects. The outfile is always CVTJRNP which uses the model file TAAJROTP and a format name of JRNOBJR.
Convert Journal Receiver Attributes. The command takes the spooled output from DSPJRNRCVA and converts the information to a data base file. Useful for accessing how many entries exist in the journal receivers.
The Convert Journal Receiver Directory command creates an outfile with one record per journal receiver for a specific journal. The API QjoRetrieveJournalInformation is used. The outfile is always JRNFILP with a format name of JRNRCVR. This is the same outfile as was used by CVTJRNA.
The Convert Logical File Member Description command converts member information from one or more logical files to an outfile named LFMBRP in a named library. For each member of a logical file, one record is output for each ‘based on’ physical file. The file can then be analyzed by various functions.
The Convert Library Attributes command builds an outfile of one or more Library objects. The outfile created is named LIBP. The outfile may then be queried for consistency or searching for specific values such as those Library objects that are specified as TEST types.
The Convert Library Authority command converts the object authority information of one, all or generic objects within a library and the library object to an outfile. The system command DSPOBJAUT operates on only a single object. The outfile name is OBJAUTP. The model file is QAOBJAUT in QSYS with a format name of QSYDSAUT.
The Convert Library Authority 2 command converts the authorities of users to library objects (not the objects within a library) to an outfile. The DSPOBJAUT command operates on only a single object. The outfile name is OBJAUTP. The model file is QAOBJAUT in QSYS with a format name of QSYDSAUT.
The Convert Library Count command adds one record to the LIBCNTP outfile which is a summary of the objects in a single library. A list of up to 300 libraries may be named or the special values *ALL or *NONSYS. The output record includes counts and sizes of typical object types as well as an estimate of the number of internal objects that will be required for a save.
Convert library data base files creates an outfile of the files that exist in a library. Options exist to specify the type of file (*PF or *LF) or *DTA or *SRC. For example, the command is useful when you have CL programs that only want to operate on source files in a library. Uses the system file QADBXREF.
The Convert Library Locks command converts any locks held on a library and any objects within the library. This allows a determination of whether any locks exist before a function that requires exclusive use of the library. The model file in TAATOOL is TAAOBJDP with a format name of OBJLCKR.
The Convert Library Locks 2 command converts any locks held on one or more object types. This allows a determination of who has the library on their library list or has made an explicit allocation of a library. The model file in TAATOOL is TAAOBJDP with a format name of OBJLCKR.
The Convert Library Object Authorities command builds an outfile of all the authorizations to objects in one or more libraries. The outfile may then be used for a function such as the CMPLIBOBJA or the CHGLIBOBJA TAA Tools.
The Convert Library Object Description command builds the LIBOBJP data base file of selected libraries (one record per library). You may specify a list of libraries (including generic names), or use the special values *LIBL, *USRLIBL, *CURLIB, *ALL, *IBM, or *ALLUSR. An omit list may also be specified.
The Convert Line Description ASYNC command converts one, generic, or all ASYNC line descriptions to an outfile. This provides a simple method of processing the information. The outfile name is always LINASCP. The model file is TAACFGUP with a format name of LINASCR.
The Convert Line Description Ethernet command converts one, generic, or all Ethernet line descriptions to an outfile. This provides a simple method of processing the information. The outfile name is always LINETHP. The model file is TAACFGPP with a format name of LINETHR.
The Convert Line Description PPP (Point to Point Protocol) command converts one, generic, or all PPP line descriptions to an outfile. This provides a simple method of processing the information. The outfile name is always LINPPPP. The model file is TAACFGRP with a format name of LINPPPR.
The Convert Line Description SDLC command converts one, generic, or all SDLC line descriptions to an outfile. This provides a simple method of processing the information. The outfile name is always LINSDLP. The model file is TAACFGQP with a format name of LINSDLR.
The Convert Member Description command creates an outfile of DSPFD TYPE(*MBR) information. Rather than using the DSPFD command directly, CVTMBRD offers more selection capability in terms of generic names, data or source, and an omit library function.
The Convert Member List command converts a list of members to an outfile using an API to access the members. The outfile format is the same as DSPFD *MBRLIST (QAFDMBRL with a format of QWHFDML), but the CVTMBRLST command allows a member name parameter and a source type parameter. Generic member names may be specified. This allows for faster creation of member lists.
The Convert Member List 2 command converts the member description information for one, generic, or all members of a file. The output file is the same as that used by DSPFD *MBRLIST. The DSPFD command does not allow a single or generic member name. CVTMBRLST2 makes it simple to create a function that processes one, generic, or all members from a file.
The Convert Menu Attributes command builds an outfile of one or more Menu objects. The outfile created is named MNUP. The outfile may then be queried for consistency or searching for specific values such as the programs that are used for menus.
The Convert Module Information command converts the module information for ILE *PGM objects and *SRVPGM objects. The information is accessed from *PGM or *SRVPGM objects as opposed to *MODULE objects. An outfile is created with one record per module with descriptive fields for the object as well as the module (such as the source file and type used to create the module).
The Convert Money tool allows a CL program to calculate such functions as how much money is owed each month on a typical mortgage calculation. Several commands are provided.
Convert Message File. The command takes the spooled output from DSPMSGD and converts most of the individual message information to a data base file. Release dependent function.
The Convert Message File Attributes command builds an outfile of one or more Message File objects. The outfile created is named MSGFAP. The outfile may then be queried for consistency or searching for specific values such as those Message File objects containing a certain CCSID.
The Convert Message Queue command converts the messages found in an external message queue (such as QSYSOPR) to an outfile. Selection criteria allows different types of messages to be converted as well as a start date and time. The API QMHLSTM is used to access the messages.
The Convert Message Queue Attributes command builds an outfile of one or more Message Queue objects. The outfile created is named MSGQP. The outfile may then be queried for consistency or searching for specific values such as those Message Queue objects containing messages.
The Convert Message Queue 2 command converts the messages found in an external message queue (such as QSYSOPR) to an outfile. This differs from the CVTMSGQ tool in that the open list QGYOLMSG API is used to allow a very large number of messages to be converted. Selection criteria allows different types of messages to be converted as well as a start date and time.
The Convert Network Attributes command converts the network attributes to an outfile. NETATRP is the name of the outfile in the library you specify. One record with unique fields for each of the network attributes is written to the file. This allows a comparison to be made with other uses of CVTNETA at different dates. See the CMPNETA command.
The Convert Network Statistics tool allows the conversion of TCP network statistics to outfiles. Options on the CVTNETSTAT command allow conversion of TCP/IP 1) Interface status, 2) Route information, and 3) Connection status. Each of the sub functions is a separate command. System APIs are used to access the data.
The Convert Object Authority command creates an outfile of authorities for one or more objects in a library. The model file is QAOBJAUT (same as used by DSPOBJAUT). The outfile is always OBJAUTP with a format name of QSYDSAUT. The system command DSPOBJAUT allows output for a single object.
The Convert Object Authority Description command converts individual authorities to an authority description of *ALL, *USE, *CHANGE, ‘USER DEF’, or *EXCLUDE. This can be helpful when dealing with an outfile such as that used by DSPUSRPRF TYPE(*OBJAUT).
The Convert Object Description command is similar to the DSPOBJD function of creating an outfile. Unlike DSPOBJD, an object name such as ‘*XYZ*’ may be specified to output a record for any objects containing ‘XYZ’ within the name field. Selection by object attribute (eg PF) or owner may also be made.
The Convert Object Description Date command is intended for converting the MMDDYY format used in the date fields of the DSPOBJD outfile. The date is returned in the CYYMMDD format. The CPP may be called directly.
The Convert Object Description 2 command creates the OBJDSCP outfile of objects similar to DSPOBJD. However, the output records contain only the object, library, and object type. The advantage of this approach is that the system does not have to determine the size of the objects. If a file has many members, the basic information can be retrieved quickly.
The Convert Object Description 3 command converts DSPOBJD information to a subset outfile using the same field names (such as ODOBNM for object name). Not all fields from the system file are included. The command is intended for the case where the program is created to run on a prior release where the DSPOBJD model file may differ and cause a file override error in a program. A list of object attributes may be specified.
The Convert Object Description 4 command creates an outfile of object descriptions based on the DSPOBJD V5R3 outfile format. This allows a program which uses the outfile that is created on a more current release to be transferred to a prior release and operate successfully. The V5R3 format is created using the QUSLOBJ API and has a format name of QLIDOBJD.
The Convert Object Description 5 command provides an outfile for most of the fields created by DSPOBJD and adds large fields for the object and save size values to allow for 15 and 20 digit fields. Edited values are also provided as separate fields. This provides a simple means of working with large sizes. The model file is TAAOBLZP with a format name of QLIDOBJD.
The Convert Object Description 6 command creates the OBJDSCQ outfile of objects similar to DSPOBJD. However, the output records contain only the object, library, object type, object attribute, user attribute, and text description. The advantage of this approach is that the system does not have to determine the size of the objects. If a file has many members, the basic information can be retrieved quickly.
Convert Object Locks. Converts WRKOBJLCK to a data base file. Uses WRKOBJLCK and CPYSPLF. Release dependent function. Useful for automating functions which need to know what jobs hold locks on objects or members.
The Convert Object Type command converts from an external object type (such as *PGM) to an integer value and/or a 4 byte character value (such as ‘0201’). For the inverse function, see CVTHEXOBJ. For a work display that allows interactive conversion, see DSPHEXOBJ.
The Convert Open Files command builds an outfile of the files that are open to a job. The outfile created is named OPNFILP. You must have *JOBCTL special authority to specify a job that is not being run under the same profile name. The QDMLOPNF API is used.
Convert Output Queue. Creates a data base file with one record per spool file in an output queue. Uses the system supported API. Useful for automating functions using the spooled files in an output queue.
The Convert Output Queue Description command creates an outfile of the descriptive information from one or more output queues. The outfile will contain such information as the number of writers assigned, the number of spooled files that exist, the connection type, etc. The outfile can then be read by a user program for a variety of needs.
The Convert Output Queue Data Queue command converts the entries sent by the system to a data queue if the DTAQ parameter is specified on CRT/CHGOUTQ. This allows a determination of spooled files that were output as opposed to the print accounting function which captures only those files that were actually printed.
The Convert Packed Field command converts a data base file containing packed or binary fields to a data base with zoned decimal fields. All character fields remain the same. The data from the original file is then copied using CPYF FMTOPT(*MAP). The new file becomes a permanent file on your system and can be used for converting from or to packed fields. This can be helpful when dealing with PCs.
Convert Program Attributes. Creates a data base file with one record per program. Uses the TAA Tool RTVPGMA (which uses an API) to access the information for one, generic, or all programs in a library, or library list. Useful for automating functions using program attributes.
The Convert Program Attributes 2 command converts program object (*PGM) information to an outfile with one record per program. This includes module information for up to 100 modules which is written as an array. This allows simple processing of programs that are made up of multiple modules. The same information as available with CVTPGMA plus the module information is output by CVTPGMA2.
The Convert Ping command captures the information from a PING command and places the results in one record written to an outfile. Each record contains the results for 5 ping attempts and the minimum, average, and maximum of all attempts. The outfile name is always PINGP. The model outfile is TAATCPM with a format name of PINGRCD.
The Convert Printer Status command converts the status information for all or generic printers to an outfile. This includes the output queue associated with the printer and the status of both the writer and the output queue. The outfile is always PRTSTSP and the model file is TAAPRTJP. The API QGYRPRTL is used along with the TAA Tool RTVDEVPRT.
The Convert Proxy Command command converts from a command object one record for each command in a proxy command chain. One record will always exist for the actual command in the chain with a type of *CMD. The QCDRCMDI API is used. The outfile is always PRXCMDP which uses the model file TAACMFOP with a format name of PRXCMDR.
The Convert PTF Group command converts the PTF groups to an outfile. There is one record output for each PTF group. This is the same information that can be displayed with WRKPTFGRP. The API ‘QpzListPTFGroups’ is used. The file name is always PTFGRPP with a format name of PTFGRPR.
The Convert PTF Group Details command converts the individual PTFs for a PTF Group or all PTF Groups to an outfile. Each record contains several fields describing the status of the PTF. This is the same information that can be displayed with WRKPTFGRP using Option 5. The API ‘QpzListPTFGroupDetails’ is used. The file name is always PTFGRPDP with a format name of PTFGRPR.
The Convert QHST command converts one or more QHST files to an externally described data base file. Allows simple processing of QHST information. For message data access, you must still know the format per message.
The Convert Record Locks command converts the record locks from all jobs holding record locks on a specific file/member. You must have *JOBCTL special authority to use CVTRCDLCK. The outfile is always RCDLCKP with a format name of RCDLCKR. The model file TAADBJMP in TAATOOL is used.
The Convert Record Lock 2 command builds an outfile of the record locks held by a job. The outfile includes information about the file, library, member, relative record number, and the status of the lock (held or waiting). The file name created is RCDLCKP. The model file used is TAADBJMP with a format name of RCDLCKR.
The Convert Registration Information command converts the data displayed by WRKREGINF to an outfile. One record is written for each exit point and program that is registered. If no programs are registered for an exit point, a record will will still be written containing the exit point information. The QusRetrieveExitInformation API is used to extract the information.
The Convert Remote Output Queue command creates an outfile of the output queues that are specified as remote output queues. The base information is the same as that produced by CVTOUTQD plus the addition of information provided by RTVHOSTNAM. The output file name is RMTOUTP.
The Convert System Reply List command converts the System Reply List entries to a data base file. This can be used to allow the Reply List entries to be transported to another system and entered using the RPLRPYLE tool.
Convert Save File Description. The information from DSPSAVF of the save information for a save file is converted to a data base file. Useful for working with the save information in a program. This includes both object and member level information.
The Convert Subsystem Description command converts the information about a Subsystem Description to one or more outfiles. All information may be converted or a specific type (such as Routing Entries). Each type is converted to a separate outfile.
The Convert SEU type command converts an SEU type such as RPG to the object type *PGM (or PF to *FILE). This can be helpful when an end user inputs an SEU type and the object type is needed.
The Convert Software Resources command provides a simpler outfile to work with than the system DSPSFWRSC command. Only the data that appears on the DSPSFWRSC OUTPUT(*PRINT) listing is converted to the SFWRSCP outfile. The model file is TAASYTXP with a record format name of SFWRSCR. Because the listing must be read by CPYSPLF, only the lower and upper case English language versions of DSPSFWRSC are supported.
The Convert Spooled File Number to API command converts a 5 byte character SPLNBR value (such as *LAST) to a 4 byte character variable containing a binary number required by the spool APIs. The command converts the special values *LAST or *ONLY as well as specific spooled file numbers. The command is useful when dealing with spool APIs.
The Convert Spooled File Number command converts the 4 digit decimal value passed from a typical SPLNBR command prompt to a 5 byte character variable for use in commands using a spooled file number. The return parameter will contain *ONLY, *LAST, or a specific 4 digit spooled file number. CVTSPLNBR is useful when writing a user command with a SPLNBR parameter.
The Convert Source Member command converts source that exceeds 70 columns of data to a format not exceeding 70 columns. This allows a tool such as EDTSRC to work with previously created DDS source such as CL or DDS. The type of source must be named (CL, CMD, DDS, or TXT). Any non supported source types are flagged.
The Convert Service Program Attributes command converts the attributes of *SRVPGM object types to an outfile named SRVPGMP in a named library. This provides a simple method of reviewing and processing service program objects.
The Convert Server Authentication Entries command converts the Authentication Entries for one or all servers to an outfile. Each record contains the name of the server and a user. You must have *ALLOBJ and *SECADM special authorities to use CVTSVRAUTE.
Convert System Level. Converts the release ID information from the form VnnRnnMnn (e.g. retrieved by RTVOBJD) to a form that is more usually displayed (e.g. VnRnMn). Useful for providing displayable information.
Convert WRKSYSSTS. Creates a data base file with one record per pool. Uses the API QWCRSSTS. Useful for determining what the attributes of a system are (such as amount of disk storage, percent used, and main storage pool information).
The Convert System Values command converts the spooled file output from WRKSYSVAL to the SYSVALP file. This provides a solution for determining the system values that exist on each release, the text descriptions and the current and shipped values.
The Convert TAA Format command is used to convert from a prior data base format to a new format for specific TAA Tools. Most conversions occur automatically when the TAA Productivity Tools are installed.
Convert Tape Save Description. The information from DSPTAP of the save information for a library or all libraries on a tape is converted to a data base file. Useful for working with the save information in a program. This includes both object and member level information. Release dependent function.
The Convert TCP Jobs command gathers information on the TCP jobs that are connected to a specific TCP port number.
The Convert Time command ensures a time format of hhmmss or hh:mm:ss (using the job time separator) from a value of *CURRENT, another hhmmss format, or a format with valid separators such as hh.mm.ss. The time is also checked to ensure it is valid.
The Convert Time to Seconds command converts a time value (HHMMSS) to a return parameter containing the number of seconds prior to midnight. For example, if the value is 030000 (3:00 AM), the return seconds would be (3600 x 3) or 10,800. CVTTIMSEC may be helpful when dealing with time values.
The Convert Time Stamp command converts a time stamp of 26 bytes to a return data structure. Individual fields in the data structure contain the the date and time in various formats such as CYMD, HHMMSS, the edited date, and the edited time. The CPP (TAATINYC) can also be called from a HLL program.
The Convert Time Zone Description command converts one, generic, or all time zone descriptions to an outfile. This provides a simple method of processing time zone information. The outfile name is always TIMZONP. The model file is TAATIMZP with a format name of TIMZONR.
The Convert Temperature command converts from Fahrenheit to Celsius or from Celsius to Fahrenheit. The command may only be used in a CL program.
The Convert to Binary 8 command converts a 20 byte character input value to a binary 8 field. This is the inverse of the CVTBIN8 tool function. Some system functions deal in 8 byte binary values. Neither CL nor RPG III handles 8 byte binary values. RPG IV does. The value to convert must be right adjusted and passed in a *CHAR LEN(20) value.
The Convert to Bytes command allows a conversion from bytes to kilobytes, megabytes, etc. The companion command is Convert From Bytes which converts from kilobytes, megabytes etc to bytes.
The Convert To Message Queue command reads the output file (MSGLSTP) from CVTMSGQ and writes the messages to a specified message queue. Only *COMP, *DIAG, and *INFO message types are written. This allows copying messages from one message queue to another. See the CPYMSGQ command for a direct method of copying messages from one message queue to another.
The Convert User Index command creates an outfile of the entries from a user index. The outfile includes fields for the attributes of the user index as well as the entry information. The outfile created is named USRIDXP.
The Convert User Profile 2 command converts the DSPUSRPRF outfile to an externally described file containing all of the fields in the QADSPUPB outfile plus individual fields for each of the special authorities, each of the supplemental groups, etc. This allows a simple query to use the individual fields for analysis.
The Convert User Space Attributes command builds an outfile of one or more User Space objects. The outfile created is named USRSPCP. The outfile may then be queried for consistency or searching for specific values such as the Auto Extend option.
Convert Volume Statistics to a Data Base File. The PRTERRLOG command is used to access the volume statistics. The data is read and placed in an output file. This is helpful for determining when bad media exists. Release dependent function.
Convert WRKACTJOB. Converts the WRKACTJOB information to a data base file. Uses system supported APIs including QUSRJOBI to access the information. Useful for determining what the active jobs are doing if anything.
Convert WRKSBS. Converts the WRKSBS information to a data base file. Useful for determining if any active jobs exist for a subsystem or the entire system.
Convert WRKSPLF. Converts the WRKSPLF information to a data base file. Uses the API QUSRSPLA. Useful for determining all spooled files for a given user, all users, or by form type.
Convert WRKUSRJOB. Converts the WRKUSRJOB information to a data base file. Uses the API QUSRJOBI. Useful for determining all jobs for a given user, all users, or on output queues.
The Debug tool is not code, but rather a technique to assist in debugging. It can also be used for any function where you are repeating several commands on a command entry display. It allows you to quickly execute a command that you had entered earlier in an interactive job. The Debug tool uses the FAVCMD tool to store the commands.
Device Status. This is a shorthand method of accessing WRKCFGSTS. The typical use is to ask for the status of generic devices such as PRT,TAP, or DKT. Useful for minimizing keystrokes to determine the status.
The Divide command provides a quotient, a remainder, and a decimal fraction after dividing a dividend by a divisor. The CL division function does not provide for a remainder. All variables must be specified as *DEC LEN(15 0).
Delete Command and Source. You name the command and it deletes both the command definition object and the source that was used to create the command. Useful for quickly cleaning up mistakes or ‘one time’ functions.
The Delete Data Base Date command deletes (or checks for deletion) records from a data base file based on a comparison of a field value and a specified date and operator. Different date formats are valid for character, zoned, packed, date, or time stamp fields. DLTDBFDAT can assist in cleaning up files.
The Delete Data Base Records command deletes records in a file based on a value in a single field. The user of the command must have all rights to the file. OPNQRYF is used internally to select the records to provide for fast processing. DLTDBFRCD provides a simple cleanup function.
Delete Dependent Logical Files. Operates on physical files, but does not delete the physical file. Useful anytime a physical must be re-created and it has dependent logicals. See also RPLPF and RBLDBF.
The Delete Deleted User Spooled Files command checks all spooled files on the system to determine if the user still exists. If the user does not exist, an action parameter determines whether the spooled file is listed or listed/deleted. This allows a cleanup of when a user profile is deleted that owns one or more spooled files.
The Delete Disabled Profile tool provides a cleanup function to allow disabled profiles to be deleted after N days. You must run a nightly job that is entered into the job scheduler by the STRDSAPRF command. Q name profiles and PWD(*NONE) profiles are never deleted. The default provides a check of what the command would do.
The Delete Duplicate Records command deletes duplicate records in a named file based on a series of key fields. By default, only a listing is output with what would occur if ACTION(*DELETE) was specified. When *DELETE is specified, the first duplicate record of a group is retained and the others are deleted.
The Delete End TAA License command provides a method of resetting the TAA license if ENDTAALIC had been used previously. This is intended for a situation where a mistake has been made or a change of plans has occurred after ending the TAA license. DLTENDLIC requires a special software code that may be requested from the TAA Productivity Tools owner.
The Delete EVENT command deletes the EVFEVENT files in one or more libraries. EVFEVENT files are created by ILE compilers and debuggers and may consume a large amount of space. Only one file will exist per library, but will contain a member for each program. If you don’t have any, using STRTRCDBG will create one.
Delete File and Source. You name the file object and it deletes both the file object and the source that was used to create the file. Useful for quickly cleaning up mistakes or ‘one time’ functions.
The Delete Generic Library command deletes one library or generic libraries. You must have *ALLOBJ special authority to use DLTGENLIB. You cannot delete a library beginning with the letter Q or the letters TAA.
The Delete Generic Profile command deletes profiles using a generic user profile name. User profiles starting with the letter ‘Q’ or owned by the system cannot be deleted. The default is ACTION(*CHECK) which does not delete any profiles.
The Delete Grace Key command is a companion command to CRTGRCKEY. CRTGRCKEY is used to allow the use of the TAA Tools for a grace period on a system that does not have a valid license. CRTGRCKEY may only be used once on a system unless a reset occurs. DLTGRCKEY provides a reset function, but requires a special software code that may be requested from the TAA Productivity Tools owner.
The Delete IFS tool allows deletion of one or more IFS objects based on selection criteria such as size, last used date, etc. You must be authorized to the TAACVTIFS authorization list and must have *OBJEXIST rights to the object to be deleted. A listing is output of the results. You cannot delete a directory type object that contains objects (see the DLTIFSDIR tool for this function). Both the DLTIFS and DLTIFS2 commands are supported.
The Delete IFS Directory command optionally deletes a directory and all sub items within the directory including other directories. The default is ‘check’ which produces a listing of what would be deleted and any errors such as ‘not authorized to delete’. Several catastrophic operations are prevented such as deleting the root (‘/’), /QDLS, and /QSYS/LIB.
The Delete IFS Owner command deletes all IFS objects owned by a user profile. This allows a simple means of IFS cleanup. You must have *ALLOBJ special authority to use DLTIFSOWN.
The Delete Job Description Library command deletes a library from the INLLIBL attribute of one or more job descriptions. This command is useful if a library has been deleted and should be removed from any Job Descriptions. No error occurs if the library is not found in a Job Description.
The Delete Job Log command deletes old job logs between a range of dates that match a list of specified job completion codes. The default is to delete all existing job logs that have had a normal completion (Completion code = 00). This allows a simple removal of job log clutter.
The Delete Job’s Spooled Files command deletes the spooled files for a specified job. The major intent of the command is to be used in batch where spooled files may be created that are not needed if the job ends normally. If a user has multiple interactive jobs and one creates excess spooled files, DLTJOBSPLF may be used to cleanup.
The Delete Library 2 command is like the system DLTLIB command, but also deletes objects that can cause DLTLIB to fail such as dependent logical files in a different library, constraints specified by ADDPFCST, receivers that have not been saved, and output queues with entries. Some exceptions exist that may prevent the library from being deleted.
The Delete Library 3 command provides a simple front end to DLTLIB and cleans up the low level messages. When the system DLTLIB command is used, low level messages are sent for each object that is deleted. DLTLIB3 cleans up the messages if the library is successfully deleted. If an error occurs, all messages will still exist.
The Delete Last Used command deletes objects in a library based on the last used date and the number of days specified. If an object has never been used, the create date is used instead. DLTLSTUSE provides a cleanup when objects are no longer being used.
The Delete Message Queue Messages command is an alternative to the RMVMSGQMSG command. DLTMSGQMSG is intended to be used when there are too many messages in a message queue for RMVMSGQMSG to be used. DLTMSGQMSG uses a different technique than RMVMSGQMSG. Messages may be deleted by a count or within a date range or both.
The Delete Object Type command allows you to delete one, generic, or all a list of object types in a library. Most popular object types are supported. If *FILE type objects are requested, all non physical files are deleted first. A spooled file describes the results. An escape message will occur if not all of the requested objects can be deleted.
Delete Object 2. Deletes a named object or generic objects without having to know the object type. Most typical programming object types (*PGM, *FILE …) are supported. An option exists to ignore any CPF2105 escape messages caused by the object not being in existence. Useful for programmed cleanup or re-create operations and particularly when generic names have been used.
The Delete Old Object command deletes old objects in a library based on the create date of the objects and the number of days specified. If your approach is to create temporary objects in a permanent library and cleanup periodically based on the create date, DLTOLDOBJ may be useful.
Delete Old QRPLOBJ Objects. Allows the clearing of the QRPLOBJ library based on a number of hours that the object has existed in QRPLOBJ. This allows a safer method of clearing QRPLOBJ for those users that do not frequently IPL. The use of CLRLIB on QRPLOBJ can cause problems if a user is still using one of the replaced objects.
Delete Old Spooled Files. Based on a specified date, it deletes old spooled files from an output queue or all output queues. An option exists to move the spooled files that are older than the specified date to a common queue so they may be reviewed and then manually deleted. The Operational Assistant will only delete certain system spooled files. DLTOLDSPLF will delete any spooled files.
The Delete Old User command checks user profiles and provides an option to delete the profile if the user has not signed on for a specified period of days. System provided profiles are never deleted. User profiles without a password are never deleted. The command provides a simple cleanup function for unused profiles.
The Delete Owned Objects command allows an *ALLOBJ user to delete the objects that are owned by another profile. The command defaults to ACTION(*CHECK) to allow a review of the objects that would be deleted.
Delete Program and Source. You name the program and it deletes both the program and the source that was used to create the program. Useful for quickly cleaning up mistakes or ‘one time’ functions.
The Delete Pending Job Log command deletes job log information (not QPJOBLOG spooled files) where the job log information is in a ‘PENDING’ status. A ‘number of days’ pending may be specified to delete only the job log information that has been pending for n days. Specific, generic, or all jobs/users may be named. The QWTRMVJL API is used.
Delete QHST. Deletes old log versions from QHST. A parameter determines the number of days to keep. Useful for cleaning up QHST.
The Delete Security Tool command allows a deletion of the sensitive security TAA Tools (those that create or change user profiles such as INZPWD and CPYUSRPRF2). With proper security in place, these tools may safely exist and be used. However, some installations may prefer to delete these tools to avoid any possibility of their use.
Delete TAA Commands. Provides a method of deleting TAA commands and other TAA objects from a command library. The concept of a command library is described in the information member “Library List Requirements” on the HELPTAA menu. The companion tool is DUPTAACMD.
Delete TAA Tool. Deletes a TAA tool from the TAATOOL library and optionally removes the source.
The Delete Unused Library command deletes libraries that have 1) no objects, 2) all objects within the library have never been used, or 3) the object within the library with the most recently last used date has not been used for a specified number of days. The default is ACTION(*CHECK) so that only a listing is output of what would be deleted.
The Delete User Profile tool is designed for Assistant Security Officers to be able to delete a user profile. QSECOFR cannot be deleted nor can any user profile in a Security Officer controlled list. The user of the command must be authorized to the TAADLTUSR2 authorization list. DLTUSRPRF2 is an option on the SECOFR2 menu.
The Delete User Profile command does more than the system DLTUSRPRF command by deleting spooled files owned by the user, listing job descriptions, and job schedule entries where the user is named. A ‘check’ option is the default to allow you to review what will be deleted.
The Delete User Spooled Files command deletes the spooled files for a named user in one, generic, or all output queues. The user profile does not have to exist which allows cleanup when the user profile has been deleted, but still is the owner of spooled files. An action parameter determines whether the spooled file is listed or listed/deleted.
Delay Command Execution. Designed for those jobs which need to operate in the restricted state and run them on an unattended basis (e.g. RCLSTG, SAVSYS). The command to be executed is entered at a workstation in the controlling subsystem just prior to the operator going home. The command parameters allow control over when the command should be executed for either a time or when a specified number of jobs exist in one or more subsystems.
The Delay Hold Spooled File command submits a batch job to QSYSNOMAX to run HLDSPLF after a delay time of a specified number of seconds. This allows a processing program to perform functions while the spooled file is the READY status.
The Delay Job Loop command simplifies the case where you are in a loop waiting for some event to occur such as a subsystem to end. Because an unusual event might occur, good coding practice would be to place a limit on the number of times the program will wait for the event to occur. DLYJOBLOOP supports a LOOPLIMIT parameter that allows the command to send the CPF9898 escape message if the limit is reached.
The Delay Job 2 command provides the capability to wait for a number of seconds. DLYJOB2 differs from the system DLYJOB command in that a wait time of less than one second may be specified. The number of seconds entered is specified as a 15/5 field. The CPP can be called directly from a HLL Program.
Delay Power down. Provides a method of powering down the system when no activity exists in a subsystem. Useful for when batch is running unattended and the system should be powered down when all work in the batch subsystem is complete.
The Delay Release Spooled File command submits a batch job to QSYSNOMAX to run RLSSPLF after a delay time of a specified number of seconds. This allows a processing program to perform functions while the spooled file is the HELD status.
The Delay Submit Job command provides a simple solution for submitting a job to start in a specified number of seconds, minutes, hours, and days. This avoids the use of SBMJOB which requires the SCDDATE and SCDTIME parameters to do a simple submit after a time delay. The DLYSBMJOB job would be placed on the QSYSNOMAX job queue with the generated SCDDATE and ENDTIME parameters and would submit the requested job (and command) after the delay.
The Demo Control Level tool provides a demonstration and standard source that can be copied to provide a procedural RPG program that handles up to 3 control breaks. After copying the source, use a source editor and follow the instructions for how to modify the source for your requirements. Both RPG III and RPG IV versions are provided.
The Demo List API Processing tool provides sample RPG code for processing the information from an API that provides a list in a user space. A working program exists with instructions within the source code for how to modify for your specific case.
Demonstrate Sub File. This is a demonstration and sample code for how to code a work subfile that makes changes to data base records. The work subfile includes typical options for display, change, copy, rename, delete (with confirmation display), and add of new data base records. A separate function is DMOSUBF2 which performs the same function for a ‘Display only’ subfile application (no changes). For a simpler solution, see CRTSFLPGM.
The Demo Subfile 3 (Array) command provides a demonstration of a subfile loaded from array data. The code provided includes comments for how to modify the source to fit your specific needs. The subfile provides an option to select one of the entries which passes back a parameter of the selected value.
The Demo Subfile 3 (Window) command provides a demonstration of a subfile loaded from array data that is displayed in a window. The code provided includes comments for how to modify the source to fit your specific needs. The subfile provides an option to select one of the entries which passes back a parameter of the selected value.
The Demonstrate Subfile 5 (Array/PosTo) command provides a demonstration of a subfile loaded from array data. A ‘Position To’ option is supported. The code provided includes comments for how to modify the source to fit your specific needs. The subfile provides an option to select one of the entries which causes the value to be passed back as a parameter.
The Demonstrate Subfile 6 (Array/PosTo/Window) command provides a demonstration of a subfile loaded from array data which is displayed in a window. A ‘Position To’ option is supported. The code provided includes comments for how to modify the source to fit your specific needs.
The Demo Subfile 7 tool provides a demonstration of using a subfile for the display of an API call. Customers can take advantage of the full source provided to create similar subfile based applications.
The DMO UIM tool provides a demonstration of using UIM for the display of an API call. Customers can take advantage of the full source is provided to create their own uses for UIM based applications.
The Demo Validate Key tool is designed to assist in cases where keys are to be added to a file, but potential miskeying errors may allow the addition of an existing record (or the existing record was miskeyed). The Validate Key program returns an array of potential alternate keys that can be checked against a data base.
The Disable Old Profile command optionally disables user profiles that have not been signed onto recently or not at all. Two retention periods may be specified for: 1) Profiles that have not signed on recently. 2) Profiles that have never signed on. Profiles created by the system or are PASSWORD(*NONE) are not considered. DSAOLDPRF may be used to minimize the exposure that profiles will be inappropriately used.
Disable User Profile. Allows an Assistant Security Officer to disable a user profile. The user must be authorized to the TAADSAPRF authorization list. DSAUSRPRF is also an option on the SECOFR2 menu for Assistant Security Officers.
Display access path. Displays or prints the detail information about an access path and each key field. A subfile of key fields is displayed with options that allow additional information about the key field and to access the field attributes.
The Display Job Accounting Codes command displays a list of job accounting codes in code sequence from both User Profiles and Job Descriptions. This simplifies understanding what Job Accounting Codes exist and where they are defined.
The Display Job Accounting Record command allows you to display the last record for a job name or user name. The display includes the same information as exists in the Job Accounting tool (JOBACG is a pre-requisite). You may roll to previous records for the user or job.
The Display Job Accounting Signon command displays the job accounting records for interactive jobs within a range of ‘From date/time’ to ‘To date/time’. All users or a generic user profile name may be entered. The user must have signed off and the Job Accounting journal entries converted for the JOBACG tool to find the information.
The Display Active Jobs command provides a display that is similar to that provided by the system WRKACTJOB command except that the user cannot perform actions against the jobs. An option exists to allow a display of any spooled files associated with the job. DSPACTJOB may be helpful if you have a menu oriented system and want to prevent users from changing, holding, or ending active jobs.
The Display Active Jobs 2 command provides a display similar to the system WRKACTJOB command except that the user can only perform the Display action against the jobs, and jobs are sorted by CPU %. System and subsystem jobs are excluded.
Display Adopt. A series of DSPxxxA commands are provided that allow a user to be authorized to various display commands so the user can display or print any object level information on the system (no data can be displayed). This is of value when dealing with functions that operate across all libraries of a system or when trouble-shooting. Authorization to all of the DSPxxxA commands is controlled by the TAADSPADP authorization list.
The Display All Data Types command lists or displays the data types that are to be included or excluded from a file or files. For example, you can display all fields that have a W (variable length) data type for files in a library.
The Display All Job Logs command provides a subfile of all QPJOBLOG files and allows them to be displayed. The user must have *JOBCTL or be authorized to the TAADSPJLG authorization list. Either the system DSPSPLF command or the TAA DSPJOBLOG3 command may be used to display the spooled file.
The Display All Proxy Commands command displays or lists all proxy commands for an actual command. An actual command may have several proxy commands either on the same chain or as separate chains. DSPALLPRX will help you if you are trying to identify all the proxy commands created for an actual command.
The Display All Save Files command displays or prints a listing of one, generic, or all save files in one or more libraries. A minimum size may be specified to help determine the large save files that are on the system. A special minimum size value *NONCLR will find all save files that are not empty.
The Display All Special Authorities command displays the special authorities for an individual user, the special authorities for his group profile, and the special authorities for each of his supplemental profiles. This allows a review of what special authorities the user is allowed to use.
The Display All Spooled files command provides a subfile of selected spooled files in a ‘display only’ function. Any user may use the command to display his own spooled files. To display spooled files owned by other users, the current user must be authorized to the TAAALLSPLF authorization list. Standard options exist to display data or attributes plus parameter controlled options.
The Display Applied PTFs command displays objects that have a PTF number applied. One, generic, or all objects by type may be displayed in one or more libraries.
The Display Area Code command provides a subfile display of the area codes for US and Canada along with the major cities in each area code. A ‘Position To’ field exists as well as the ability to select only a specific state or province. Time zone information is also provided. Helpful for determining where someone is located when an area code is known or determining what area codes exist by state.
The Display ARP (Address Resolution Protocol) Table command displays or prints the ARP table information for a specified line description. Address Resolution Protocol allows physically distinct networks to appear as if they were a single, logical network. The QtocLstPhyIfsARPTbl API is used to extract the values.
The Display ASP (Auxiliary Storage Pool) Attributes 2 command displays or prints a brief description of the important status and description information about an ASP. This includes the total storage capacity, the percent used, the amount of remaining storage, the type of ASP, the threshold percent, and the amount of overflowed storage if any.
The Display ASP Status 2 command provides an interactive display of the disk units by ASP. The information displayed is taken from WRKDSKSTS for each disk unit. Summary totals are shown for each ASP. DSPASPSTS provides a simple means of helping to manage an ASP.
The Display Audit Command command displays or lists audit records for a specific user for the AUDLVL(*CMD) function. The AUDLOGP file (AUDLOG tool) is used. The user must be specified as CHGUSRAUD AUDLVL(*CMD) which causes an audit entry for each command executed (including commands run in CL programs or REXX procedures). DSPAUDCMD provides a tailored solution for the ‘T CD C’ journal entries.
Display Audit Log 2. Displays or prints the audit log journal (QAUDJRN) with various selection options. This is the old form of DSPAUDLOG which is not supported for newer audit entries.
The Display Audit Record command works with the files created by the AUDLOG tool to display the last audit record for a user or job. The display includes the same information as exists in the DSPAUDLOG detail record display including the ability to use F6 to access the details of the audit information.
The Display Auth List Objects 2 command differs from the system DSPAUTLOBJ command by 1) providing *IFS and *DLS objects in addition to library objects and 2) allowing a generic name or all Authorization Lists. The full path name (up to 5000 bytes) is displayed or listed.
The Display Based On File command displays the based on physical file members for a logical file. This provides a simpler means of determining the based on file members rather than using DSPFD. Other information about the access path is also displayed.
The Display File CCSIDs command displays either a total of the CCSIDs that exist in a data base file or the CCSIDs for the individual fields. If different CCSIDs are used within the file, different processing may be required. DSPCCSID allows you to determine if a file uses a standard CCSID for all character fields and what the value is.
The Display Calculator command provides a simple calculator with add, subtract, multiply, and divide functions. The command is intended for simple calculator needs on any type of workstation.
The Display CLP Call Parameters command provides a spooled file with one or all of the Call statements in a CL source member printed and the attributes of the passed parameters. The columnar display can make it easier to understand the important characteristics about the parameters.
The Display CLP Command command displays commands from the CLPCMDP file created by CVTCLPCMD. Various search criteria such as the source file library may be named. DSPCLPCMD provides a fast access for where a specific command name has been used.
The Display CLP Count command counts the number of lines of commands in a CL source member, generic members, or all members in a source file. Comment lines and blank lines are also counted. A percentage of comments is provided. DSPCLPCNT provides a better understanding of the amount of actual source versus a count of the number of statements in a source member.
Display CLP DO Groups. Displays the DO groups (in a similar manner as RPG) in CLP source. This provides a simple means of determining where DO group errors exist. Useful for program comprehension and fixing the problems caused by the CL compiler diagnostics relative to unbalanced DO statements. See also PRTCLPDO.
The Display CLP Parameters command provides a spooled file with one line for each parameter passed to the program. The columnar display can make it easier to understand the important characteristics about the parameters. The source member must be identified.
The Display CLP Source command displays or lists the source for a CLP type program (CLP, CLP38 and CLLE). If the source does not exist for a CLP or CLP38 program (non-TAA), a prompt occurs asking if RTVCLSRC should be used and a display occurs after retrieval. If a TAA program is specified and the user is authorized to the TAASRCACC Authorization List, the source in the TAA Archive is displayed.
The Display CLP Variables command provides a spooled file with one line for each variable declared in the program. This is basically the same information that is available on a compiler listing, but the information can be accessed faster with DSPCLPVAR. Sequence number references are not included. The variables appear in alphabetical sequence with their attribute information.
The Display Command Authority command displays the required authorities and typical exceptions for popular system commands. Not all commands are supported. The display describes the authorities (such as *OBJOPR or *READ) that are required to operate on an object. Notes also appear if applicable.
The Display CMD Count command counts the number of lines of commands in a CMD source member, generic members, or all members in a source file. Comment lines and blank lines are also counted. A percentage of comments is provided. DSPCMDCNT provides a better understanding of the amount of actual source versus a count of the number of statements in a source member.
The Display Command Help command displays the help text for a system or user command including commands the user is not authorized to. The command is useful for such functions as attempting to simulate the system command line function. The QCAPCMD API is used.
Display command keyword. Displays a subfile of keywords used by commands. Two special values allow access to the files supplied in TAATOOL for access to all commands in QSYS and all commands in TAATOOL. Assists in understanding where keywords are used and in selecting a keyword name.
The Display Command Keyword 2 command displays or prints a simple list of the keywords used by a command. QSYS and TAATOOL command information is supplied in TAATOOL. User commands must be converted to a file using CVTCMDKWD.
The Display Command Parameters command provides a spooled file with one line for each parameter of a command. The columnar display can make it easier to understand the important characteristics about the parameters. The source member must be identified.
The Display Command Source command displays or lists the command source for a command. If the source does not exist for a non-TAA command, a prompt occurs asking if RTVCMDSRC should be used and a display occurs after retrieval. If a TAA command is specified and the user is authorized to the TAASRCACC Authorization List, the source in the TAA Archive is displayed.
The Display Color Attributes command displays the various combinations of the COLOR and DSPATR keywords. A color display is needed. The intent of the display is to allow you to select the proper combination of how you want a field displayed.
The Display Completion Codes command displays the job completion codes described in the CPF1164 message. This provides a quick review.
The Display Create Date command provides a display or listing of objects with selection on the create date and time. The default displays the objects in descending create date and time order. DSPCRTDAT may be useful in understanding recent changes.
The Display Create User command displays or lists objects and compares the ‘create user’ to the ‘current owner’. A specific ‘create user’ may be selected. Differences are flagged. DSPCRTUSR may be helpful in understanding changes that have occurred.
The Display Current User command is similar to the WRKUSRJOB system command except that the current user of the job is also shown and no change options are allowed. This allows support for jobs that swap profiles to be displayed. Only active jobs are displayed.
The Display Date command provides a convenient method of displaying information about the current date or any date in a range of Jan 1, 1941 to Dec 31, 2040. The fully spelled out date, the day of the week, the week of the year, and other values are shown.
The Display Date Formats command displays the valid formats for data base date fields (Type = L). Examples of each DATFMT option are displayed. Job date formats are also displayed along with the timestamp layout (Type Z).
Display Data Base. Displays an externally described file by placing the field names and values for a single record on a display. Converts packed to character and edits fields. Allows either relative record number or a key. Rollup and down are supported. Useful for problem determination or debugging.
Display Data Base File. Provides a simple front end to the RUNQRY command. This allows a simple review of the data in any data base file and supports selection criteria. The results are displayed or printed and are always provided in arrival sequence order.
The Display Data Base File Attributes command displays two pages of the important attributes of data base files. Function keys allow access to other ‘display only’ options. The command provides a simpler interface than using the system DSPFD command.
The Display Data Base File Allow Functions command displays the options for ‘allow update’ and ‘allow delete’ that may be set for physical data base files. A listing is produced of either all files or only those which have specified either of the ‘allow’ options. The intent of DSPDBFALW is to allow a review of these options.
The Display Data Base Damage command checks for damage in the data base file descriptive information. Each file processed is used by CHKOBJ, RTVOBJD, various forms of DSPFD, and DSPFFD. An outfile of the damaged files is optional. The data itself is not checked. DSPDBFDMG is intended for the case when an abnormal system termination has occurred and you suspect data base damage.
The Display Data Base File Data command displays or prints data from a single record in a file (using Relative Record number) or from a passed in image of a record (such as a journal entry). The command will operate on any externally described file. The output is one line per field whether a subfile or listing occurs.
The Display Data Base Field command displays the attribute information for a field in a physical file or a single format logical file. The attributes include such things as the length, decimal positions, buffer position in the record, text, and column headings.
The Display Data Base Join Files command displays or lists one or more join files in one or more libraries. The From and To file information is provided along with the name of the keys from each file.
The Display Data Base File by Key command displays or prints records from a single format data base file in keyed sequence. The key fields appear as the first fields in the listing. Any remaining fields that fit into the 378 maximum wide print line are also listed. DSPDBFKEY is a front end to the PRTDB key which allows listing fields by name.
Display data base relations. Similar to the system command DSPDBR except that the list of dependent files is displayed in a subfile. Options exist to display the file attributes or the access path description.
The Display Data Base File Statistics command displays usage statistics for a physical file data member. Each dependent logical file is also shown. The system data base statistics are used which are reset at each IPL.
The Display DDS Count command counts the number of lines in a DDS source member, generic members, or all members in a source file. Comment lines and blank lines are also counted. A percentage of comments is provided. DSPDDSCNT provides a better understanding of the amount of actual source versus a count of the number of statements in a source member.
The Display Dependent Logical command provides a display of the dependent logical files of a physical file. A physical file must be specified for the FILE parameter. An option exists from the display to access other options such as the access path information.
The Display Device Character command displays the characters for the hex values X’40’ - X’FF’. This can be helpful when attempting to provide a unique character for the display. A second display is available to show the typical characters required to cause underlining, hi-lighting, etc.
The Display Default Records command displays the Relative Record numbers of the records in a file that match the default record used by the system when adding a new record. It is possible for an application or a utility like DFU to add a default record as an error. DSPDFTRCD will find these conditions, but not all may indicate an error. You must decide based on your application.
The Display Deleted Space command displays the amount of deleted record space that exists in one or more libraries. If variable length fields exist, the allocated length is considered rather than the maximum record length. An omit list of libraries may also be specified.
The Display Disk Status command displays or lists information about the disks attached to the system. The display differs from the system WRKDSKSTS command in that fewer statistics are shown, but the data is grouped by ASP with additional information about each hardware resource. The data is accessed from the TAA CVTDSKSTS command.
The Display DST (Daylight Savings Time) Date command displays or lists the start and end date/times for daylight savings time for a time zone in a specific year. The system support for Time Zone Descriptions does not include actual dates of change.
The Display Distribution Queue command is a simple front end to the system WRKDSTQ command. Only a display is provided so no changes are allowed. WRKDSTQ is set as *PUBLIC(*EXCLUDE). DSPDSTQ adopts the authority of QSECOFR so that any user may review the contents of a distribution queue or all distribution queues.
The Display Data Area Description command displays or prints the attributes of a data area. The data area value is not shown.
The Display Data Queue command displays or prints the entries of a data queue and the data queue attributes. An API is used to extract the information which does not remove any entries. The entry may be displayed in character or hexadecimal. If a *KEYED data queue exists, the key information may be displayed.
The Display data queue description command displays or prints the attributes of a data queue object. The information includes the create attributes plus the current number of entries and the number of entries that can be made before an overflow occurs.
The Display Data Base Data Types command displays a listing of the data base types that may be entered in DDS and appear in DSPFFD output. This provides a simple online aid.
Display Duplicate Command is intended to check if duplicate command names exist in two libraries or in one library and the rest of the system. Having duplicate command names can be an integrity or security exposure. The typical uses would be to ensure your user command names are not found in either QSYS or TAATOOL.
The Display Duplicate Field command checks a specific field or fields in a data base member for duplicates. The file is sorted on up to 6 fields and a program checks for duplicate values. Up to 3 print fields may be specified to help identify the records that have duplicate values.
The Display Duplicate Job Queue Entries command displays or lists job queue names that are duplicates in different subsystems. DSPDUPJBQE can be used to help identify problems where the same job queue is used
The Display Duplicate Jobs command provides a display of jobs based on a job name. A subfile of jobs that match the selection criteria is displayed. A detail display of simple job information is available as well as a function key to access DSPJOB data. The major intent of the tool is to allow a call to a DSPDUPJOB program with a return parameter list. This allows the end user to select a job for further processing when duplicate jobs exist.
The Display Duplicate Key command checks a keyed file that has not been specified for Unique keys to see if any duplicate keys exist. The file is read in keyed order per the key fields defined for the file and compared to the previous record. The relative record numbers of any duplicates are described.
The Display Duplicate Profile Attributes command displays or lists the profiles that have duplicates for such attributes as Initial Program, Job Description, User Class, etc. This provides a review of where changes may be needed.
Display Edit Code. Provides an online version of the Edit Code table (e.g. commas, zero balances to print, etc.). The simple command is more convenient than looking anywhere else.
The Display Empty Data Area command displays one or more data areas that have no value or a zero value (*DEC type *DTAARA). A flag may be set if the data area has not been changed (such as by CHGDTAARA) in the last n days. An option exists to list all data areas. DSPEMTARA can be helpful in cleaning up unused data areas.
The Display Empty Authorization List command displays Authorization Lists (not owned by QSYS) that do not control any objects. This includes library objects, IFS objects, and DLS objects. An option exists to include all Authorization Lists (not owned by QSYS).
The Display Empty Data Base File command displays data base files that have no members. A flag may be set if the data base file has not been used in the last n days. An option exists to list all data base files. DSPEMTDBF can be helpful in cleaning up unused data base files.
The Display Empty Data Queue command displays one or more data queues that have no entries. A flag may be set if the data queue has not been changed (such as not having received an entry) in the last n days. An option exists to list all data queues. DSPEMTDTAQ can be helpful in cleaning up unused data queues.
The Display Empty IFS command is a front-end to DSPIFS to provide a listing of the empty IFS stream files. Stream files that have an object size of 0 are displayed. Note that this is not the allocated size of the stream file. The DSPIFS command is used internally and the output appears with the title of ‘Display IFS’.
The Display Empty Job Queue command displays one or more job queues that have no jobs. A flag may be set if the job queue has not been used (such as not having any jobs added) in the last n days. An option exists to list all job queues. DSPEMTJOBQ can be helpful in cleaning up unused job queues.
The Display Empty Libraries command displays or lists one or more libraries that have no objects. The command performs quickly as the simplest form of the API to retrieve object information is used.
The Display Empty Members command displays or prints the empty members for one, generic, or all files in one or more libraries. Size information is also supplied to point out space savings that can be achieved for members that are no longer needed. The size information includes the data and access path size, but not the member description object which can be up to 20K bytes.
The Display Empty Message File command displays one or more message files that have no message IDs. A flag may be set if the message file has not been used in the last n days. An option exists to list all message files. DSPEMTMSGF can be helpful in cleaning up unused message files.
The Display Empty Message Queue command displays one or more message queues that have no messages. A flag may be set if the message queue has not been changed (such as not having received a message) in the last n days. An option exists to display all message queues. DSPEMTMSGQ can be helpful in cleaning up unused message queues.
The Display Empty Output Queue command displays one or more output queues that have no entries. A flag may be set if the output queue has not been used (such as not having any spooled files) in the last n days. An option exists to list all output queues. DSPEMTOUTQ can be helpful in cleaning up unused output queues.
The Display Empty Save File command displays or lists one or more save files that have no objects. The default is to bypass save file names beginning with Q as there may be many PTF save files in existence.
The Display Empty User Space command displays or lists one or more User Space objects where the User Space contains only the initial value described when CRTUSRSPC was used. An option exists to list all User Space objects. DSPEMTSPC can be helpful in cleaning up unused User Space objects.
Display Error Message. Provides a solution for handling unexpected escape and diagnostic messages from an interactive CL program. The command should follow a MONMSG command and the user sees a display of both the escape and diagnostic messages on a single display. Access to 2nd level text and the message description is provided.
The Display Exclusive Locks command displays or lists the objects/members that have exclusive locks. This can be a very slow running command if many physical file objects are specified to be checked as CVTOBJLCK must be used on each to determine if any members are locked exclusively. DSPEXCLCK can assist in determining what cannot be processed because of exclusive locks.
The Display Function Usage 2 command will show a summary of the function IDs used on this system, making it easier to see the overall picture of these than using the DSPFCNUSG command of the system.
Display File Data Queue. The code is an example only of how to handle a display file with the data queue parameter. This allows the program to receive control when either a workstation enter key or a data queue entry arrives. Two examples are shown 1) an interrupt example, and 2) a refresh example.
Display field attributes. Displays the attributes of a single field in a file. The file can be a physical or a single format logical. The CPP can be invoked from any HLL program. Useful for applications which want to allow the user to access the specific attributes of a single field.
The Display Field Use tool allows a ‘where used’ function of the fields in externally described files. The Display command provides access to the definition of a field and the files that use the field. The CVTFLDUSE command must be used periodically to convert the system DSPFFD outfile information to files used by DSPFLDUSE.
Display format. Displays a subfile of the fields in a physical file or a single format logical file. The subfile display provides enough information for most uses and a detail display of seldom used attributes is also available for each field. A print option is also available.
The Display Format Sequence command displays the fields in a physical or single format logical file in various sequences such as by field name or type and length. When a file has a large number of fields, DSPFMTSEQ may be helpful in reviewing the fields in the format.
The Display First Spooled File Status command displays the status of the first spooled file on an output queue for the current user. It describes how many other spooled files and pages must be printed before the users first spooled file is printed. This provides a simple function for end users to determine when their spooled file will be printed.
Display file 2. Displays a list of files matching a generic name in a subfile and allows options for such functions as the file attributes, the access path information, the format of the file, any data base relations, and to display the data.
The Display Generic Object command displays, prints a list, or creates an outfile of objects. A single object, all objects, a generic name, or a name including wild card characters may be used. If a display is requested, an option exists to use the TAA Display Object Description command which provides more information about the object.
The Display Group Profile command displays or prints the members of a group and detail information. The command is an improvement over the system DSPUSRPRF OPTION(*GRPPRF) function in that information about the individual members is displayed.
The Display Group Profile Indicator command displays whether a profile is a group profile (has members in its group). You must have *ALLOBJ authority to use DSPGRPPRFI. Use the DSPGRPPRF command to list the members of the group.
Display Hex and other things. Provides a convenient interactive method of converting 1) a binary value to decimal 2) a decimal value to binary 3) an EBCDIC value to Hex 4) a Hex value to EBCDIC 5) K,M,G,T values to decimal. The command also provides convenient displays for 1) Bit settings 2) Powers of 2 to the 54th 3) EBCDIC values 4) Prime numbers up to 255.
The Display Hex Object Type command allows the input of an external object type (such as *DTAQ) and displays the internal hexadecimal value (such 0A01). It also allows the input of an internal object type (such as 0201) and displays the external object type (such as *PGM). The display may also be used for conversions.
The Display USA Holidays command displays a window of the major US holidays for a specific year. The actual date and day of week are also displayed. A print option and an outfile option are also available.
The Display IFS command provides a display or listing of IFS objects. The outfile from the TAA command CVTIFS is used for the data. Different selection criteria can be specified as well as a sort on one of the fields. A standard listing format is used. DSPIFS can be used to eliminate the need to write simple query functions of IFS data.
The Display IFS Auditing command displays the auditing attribute of IFS objects. Selection may be made on the type of auditing including *NONE. DSPIFSAUD assists in understanding what is being audited. To specify auditing for an IFS object, use CHGAUD.
The Display IFS Authorities command displays or prints the IFS authorities from the file created by the CVTIFSAUT TAA command. You must first run CVTIFSAUT for the IFS objects that you want to analyze. DSPIFSAUT provides a simple query like function including selection capability such as by user (including *PUBLIC), by type of authority (e.g. *CHANGE), by authorization list, etc.
The Display IFS Entry Description command provides a command to display the attributes of an IFS entry. WRKLNK supports an option for this, but it is not a command. Additional information is provided by DSPIFSED and a print option exists.
The Display IFS Owner command displays or lists owned objects in the IFS (does not include objects in libraries). The system DSPUSRPRF command does not display this information. The QSYLOBJA API is used to extract the information.
The Display IPL History command displays or lists the dates and times that an IPL has occurred within a range of dates. The inclusion of the normal power down entries is optional as well as IPL completion. You must be using the CVTQHST2 tool command to first convert the QHST information.
The Display IPL Status command displays the information about the current IPL status and the settings for the next IPL. An option exists to access the TAA Display IPL Attributes command. DSPIPLSTS provides a simple review of IPL information.
The Display Job Description Libraries command provides two functions for one, generic, or all job descriptions: 1) A simple listing of the libraries in each job description 2) A check for any non-existent libraries. The output is either displayed or listed.
The Display Job Log 2 command displays or prints a job log with or without selection criteria. For example, a job log can be displayed or printed with one or more specific message IDs, generic message IDs, or one or more message types. This provides a way to ‘net out’ a job log to look for specific messages.
The Display Job Log 3 command provides a different method of viewing a job log. The messages are displayed on an 80 byte wide display using a subfile with one line per message plus a detail display option. Different positions within the subfile can be quickly displayed along with a scanning capability to find any character string.
The Display Job Log 4 command allows a user who has specific *USE authority to the TAASPLSEC authorization list to be able to display any job log on the system. Program adopt and group adopt are not considered valid.
The Display Job Log 5 command provides a different method of viewing a job log and attempts to display the last escape message (and associated messages) first. The messages are displayed on an 80 byte wide display using a subfile with one line per message plus a detail display option. Different positions within the subfile can be quickly displayed along with a scanning capability to find any character string.
The Display Job Performance command lists job performance information for the current job. The RESJOBPERF command (part of the JOBINF tool) should first be used to begin capturing the information. After some commands are entered, DSPJOBPERF may then by used to display the information.
The Display Job Queue command provides a display that is similar to that provided by the system WRKJOBQ command except that only a single job queue may be displayed and the user cannot perform actions against the jobs. DSPJOBQ may be helpful if you have a menu oriented system and want to prevent users from changing, holding, or ending jobs on a job queue.
Display Job Queue Attributes. Provides a method of displaying or printing the attributes of a job queue. The current status information is also provided.
The Display Job Schedule Calendar command displays the jobs that are scheduled to run from the system job scheduler for the next 7 days (beginning tomorrow). The listing describes the jobs to be submitted by date and time. DSPJOBSCDC provides a good review of the jobs that will be submitted by the system job schedule function.
The Display Job Schedule Description command displays or prints a single job schedule entry. The command is usually entered as an option from the DSPJOBSCDE subfile, but may also be entered directly. The description may be displayed or printed.
The Display Job Schedule Entries command is a ‘display only’ function similar to the system WRKJOBSCDE command. This allows making the WRKJOBSCDE command private so that only authorized users may make changes while the *PUBLIC user can use DSPJOBSCDE. An option exists to display the entries in next job schedule date order.
The Display Job Schedule Result command displays the results of Job Scheduled jobs (how they completed) for the last submission. The JOBACG tool must be in use and the job accounting entries must be current for the completed Job Scheduled jobs to obtain meaningful results. DSPJOBSCDR assists in understanding what is happening to Job Scheduled jobs.
Display Job Start Attributes. Displays the job start attributes about any job on the system such as the job queue that was used, the subsystem, the time the job was started, the user who submitted the job, etc. Depending on the status of the job (on the job queue, active, etc.), some of the information is not provided by the system to allow it to be displayed.
The Display Job Type Description command displays the codes and descriptions of different job types. Both the three character codes used on WRKACTJOB and the one character codes used in APIs are displayed with the corresponding descriptions.
The Display Job 2 command is a more powerful version of the system DSPJOB command. DSPJOB2 supports options for DSPJOB and DSPJOB OUTPUT(*PRINT) and all of the detail options available on the DSPJOB menu. When the option completes, the subfile is re-displayed. DSPJOB2 also allows options for all jobs, all users, job status, and job type.
The Display Job 3 command allows a user who has *USE authority to the TAAJOBCTL authorization list to perform DSPJOB functions for a job that is not his own. This allows trusted individuals (such as programmers) to have DSPJOB capability as if they had *JOBCTL special authority without directly specifying *JOBCTL in their user profile.
The Display Journal Attributes command is similar to the system WRKJRNA command. DSPJRNA provides a ‘display only’ function. No Function keys allow a WRK type of command. No journal entries may be displayed. DSPJRNA may be useful for operations personnel who do not need WRK type functions.
The Display Journal Codes command displays the journal codes, entry types, and sub types in a window. This can be helpful in determining what the codes mean or which code to look for.
The Display Journal Object Counts command displays or lists counts of object types that are being journaled to a named journal. This includes data base files, members, access paths, data areas, data queues, IFS objects, command definitions, libraries, and journal receivers.
The Display Journal Receiver Directory command displays or prints the list of journal receivers for a specific journal. This is a ‘display only’ function that may be safely used by operations personnel.
The Display Journal Receiver Attributes 2 command is similar to the system DSPJRNRCVA command, but does not provide for an F10 key which allows a WRK command. Only attributes of a journal receiver are displayed (not the journal entries).
The Display Logical File Member Description command displays or prints information about a logical file member. The first based on physical file member information is also displayed.
The Display Library Authority command provides a listing of one, generic, or all objects in a library with the individual authorizations to objects. One line is output for each authorized user. Selections can be made by different parameters such as object type.
The Display Library Job Description command displays or lists one or more libraries and job descriptions in one or more libraries that contain a specified library name. This allows you to determine what libraries are specified within job descriptions.
The Display Library Size command displays or lists a summary of a library with size and count information. One, generic, or many libraries may be requested to be included. The library object record is included in the size and count of objects. An outfile may also be requested which contains many additional fields. The outfile model file in TAATOOL is TAALIDHP with a format name of LIBSIZR.
Display library source files. The command allows you to name a library and a spooled file is displayed of the source files in the library. The spooled file may also be printed.
The Display Library 2 command displays or lists objects, data members, and source members in a named library. Summaries of each section are shown. More information is shown than the system command DSPLIB, but only a spooled file exists (not an interactive display). DSPLIB2 can be helpful when reviewing the contents of a library.
The Display Last Job Log command displays the last QPJOBLOG file for the current user based on the job number. This simplifies displaying the job log for programmers and operators when the last submitted job fails.
The Display Last Object command displays information about the last object name of a generic group of objects. The default is for all object types. If the same name exists for different object types, the last object type (per system order) determines the object that is displayed. If you are naming objects using a generic technique, DSPLSTOBJ can assist in providing information about the last name assigned.
The Display Last Password Change command lists all or generic profiles by the date the password was last changed. Profiles that are set to PASSWORD(*NONE) are bypassed. The default is for ascending sequence.
The Display Last Signon command allows you to sequence user profiles by the last signon date/time and select on a range of ‘From date/time’ and ‘To date/time’. All users or a generic user profile name may be entered. This can be used to display users who have signed on in the last n hours or have a last signon prior to n months ago.
The Display Last Spooled File tool supports three commands - DSPLSTSPLJ = Displays the last spooled file of a job, DSPLSTSPLQ = Displays the last spooled file in an output queue, and DSPLSTSPLF = Provides an option for either of the previous commands. This provides a simple means of accessing the spooled information for the last function performed.
The Display Last Use command displays or prints a listing of one line per object in a library identifying the create date, the last used date, and the use count. Objects that have never been used are always listed. An option exists to list those objects that have not been used prior to a specified number of days. DSPLSTUSE helps determines what objects may be deleted because of lack of use.
The Display Member Capacity command displays one line per member describing the current number of records and the record capacity. Multiple libraries and a generic file name may be used. A specified percentage allows a flagging of those members which are nearing their record capacity. The command defaults to list only those members which are flagged.
The Display Member Description command displays or prints the information about a specific member such as the number of records, the last date change, the number of increments used, and physical file member statistics.
The Display Member List command is intended for multi-member data files. One, generic, or all files in a library may be listed. A heading line is printed for each file. One line is printed for each member in the file with information such as the create, change, and last used dates, number of records, etc.
Display members. Displays a list of members in a data base file using a subfile and allows options to display the member description and to display the data.
The Display Member Statistics command displays or prints the member statistics captured by the CVTMBRD command. The member statistics include fields such as the number of reads, updates, deletes, access path builds, etc. Different sequences can be specified. Member statistics are only kept by the system for physical file members.
The Display Multi-Format Files command displays or lists Logical Files that have either multiple formats or are joined files. The dependent files are also listed. One or more libraries may be specified with a request for a single, generic, or all files.
Display Money. This is a series of commands to help analyze how money will grow at a specific interest rate, what the monthly payment of a loan will be etc. The commands are useful for evaluating different approaches to the handling of money. The commands include growth, loan, present value, level increase, annuity, fund, and distribution. A menu is provided to allow easy access to all of the commands. Specify GO DSPMONEY.
The Display Monitor Message command displays the monitorable messages associated with a system command. If a translate message file exists before QSYS on the library list, it is used to supply the message text. Avoids having to look in a manual for the information.
The Display Moon command displays the dates of the full moon for a specific year. The new moon occurs about 14 days earlier than the full moon. The 1st quarter moon occurs about 7 days earlier and the last quarter moon occurs about 7 days after the full moon.
The Display Message Count command displays a list of message queues and the number of messages in each. By default, message queues without any messages are bypassed.
The Display Message Queue by Date command provides a simple listing of the messages in a message queue by date and time. This provides a review of how old messages are in a message queue.
Display Message Data. Displays the 1st and 2nd level text of the message and the message data fields including the start position. Useful when working with message data to determine which field you want and where in the message data it is located.
The Display Message File Attributes command displays the attributes of a Message File. What can be of particular importance is to be able to see the CCSID assigned to the file. The value determines if a Message Description is converted for an Add or Retrieve.
Display Message Queue Attributes. Provides a method of displaying or printing the attributes of a message queue. The current status information is also provided.
The Display Message Queue Inquiries command displays or lists inquiry messages and their replies from a message queue such as QSYSOPR. The formatting allows a better review than the DSPMSG command. A detail option for additional information is available.
The Display Message CCSID command displays the actual CCSID of a Message Description. DSPMSGSID is designed as a problem determination aid. When a Message File has a CCSID of 65535, the CCSID of the Message Description is ignored and 65535 is used because no conversion will occur at the time of an ADD/CHGMSGD or if the text is retrieved (such as by SNDPGMMSG).
Display Message Text. This allows the entry of a system message ID and the command uses DSPMSGD to display the message. The command determines the message file and library needed based on the message ID provided. Useful for help desk operations or simplifying the display of any message.
The Display Message Type command provides a simple display of the codes and descriptions the system uses for the RCVMSG RTNTYPE parameter.
The Display Message Use command displays the commands that use the same monitorable message. Useful in determining which command has sent a message when it is not clear.
The Display Message Use 2 command reads the outfile created by the SCNEXTMSGF TAA Tool and creates a listing of the message ID and the command name that sends the message if it is known. Only system commands that send escape messages can be identified. Diagnostic messages and messages from APIs cannot be identified.
The Display Messages in a Window command allows a message subfile to be displayed as a window. The messages in the current program message queue are displayed. The command is intended for use in in a CL program or executed from a HLL program using QCMDEXC.
Display Message 2 allows several selection criteria to minimize the number of messages that would be displayed or listed. For example, you can display by message ID, message type, job, user, start/end date/time, or the sending program. The DSPMSG2 command may be used on any message queue, but would most likely be used with QSYSOPR.
The Display NetServer Attributes command displays or lists the attributes associated with the i5/OS NetServer. This includes both the current and pending attributes.
The Display Net Server Statistics command displays the current NetServer statistics. The RTVNETSVRS command is used internally which runs the QZLSOLST API.
The Display Non Use command command lists objects that have not never been used along with size information. This can assist in cleanup of the system. Because of the way last used information is handled on multi-member data base files, the information may not be accurate on multi-member files.
The Display Object command provides various DSPxxx commands for most object types. While the command is intended for use as a menu option where the object and object type are already known, it may be used as a general purpose DSPxxx command. In some cases WRK commands are used when no corresponding DSP command exists. Either a system or TAA command is used.
The Display Object Auditing command displays all audited objects in a list of libraries or all libraries. Auditing of an object is set by the CHGOBJAUD command. Options exist for selection by object type, a list of omitted libraries, and the library type.
The Display Object Damage command displays object damage as reported by the object list API (QGYOLOBJ). This may not be the only damage to an object. If damage is reported, you should re-create any such objects.
The Display Object Description 2 command provides a different interface to DSPOBJD information. If multiple objects exist, a subfile is displayed which may contain multiple libraries. If a single object exists, only the detail display is presented. The detail display contains combined information from the various DSPOBJD displays. Access to additional object information is provided as well as a search pattern.
The Display Object Description 3 command is like the DSPOBJD command outfile support with the exception that a list of omitted libraries may be named. This can be helpful when processing a special library value such as *LIBL, *USRLIBL, *ALLUSR, or *ALL where you do not want certain libraries that would normally be included.
The Display Object Description 4 command is a problem determination aid and is similar to DSPOBJD2. DSPOBJD4 allows any object description on the system to be displayed if the user has *USE authority to the TAADSPOBJ4 authorization list. ‘Display only’ functions for additional object level information are also provided for most object types. No data can be displayed.
The Display Object Exceptions command lists one or more objects that are saved with storage freed, locked, damaged, or where the storage requirement has overflowed the ASP. Multiple libraries may be searched.
The Display Object Journal Attributes command displays or prints the journal attributes for a physical file, a data area, or a data queue. This is the same information that may be seen using DSPOBJD and rolling up several screens.
The Display Object Locks command is similar to the system WRKOBJLCK command except that only display functions exist. This is designed for a user who should not be able to change or end jobs. The QWCLOBJL API is used.
The Display Object Size command displays or lists objects and their sizes. Selection can occur on a generic object name, object type, object attribute, and owner. Sequencing can be requested by size. DSPOBJSIZ provides a simple review of objects by size.
The Display Object Source Change command lists objects in a named library where the change date of the source member that was used to create the object is more current than the object create date. If the member does not exist, it is flagged. If a program was created from modules, the source for the module with the most current source change date is used for the comparison.
The Display Object Type Description command displays the valid object types on the system in a subfile and allows a detail display with a one paragraph description. A print option is also available to print a one line listing or a paragraph for each object type.
The Display Object 2 command provides a subfile display of one or more objects. The display format is similar to WRKOBJ, but supports only a single option 5=Display. This invokes the TAA DSPOBJD2 command which provides other display options such as DSPOBJAUT and the F8 option which changes based on the object type to allow a display of additional details.
The Display Online Information command provides a display of many of the online TAA tools such as DSPEDTCDE. Access is also provided to the DSPPERTAA menu. The command avoids having to remember the individual command names to access online information.
The Display Outfile command displays the model files associated with commands that provide an outfile. Both system and TAA commands are supported. A subfile is displayed which includes the model file and format used. An option exists to display the fields in the model file.
The Display Outfile Format command displays the fields in a format of the model file for commands that create outfiles. Many DSP commands and CVT commands support an outfile. Both system and TAA commands are supported. If multiple outfiles exist for the command (eg DSPFD), the DSPOUTFILE command is used to allow a selection. DSPOUTFMT may only be used interactively.
Display Output Queue Attributes. Provides a method of displaying or printing the attributes of an output queue. The current status information is also provided.
The Display Owned Objects command is similar to the system DSPUSRPRF TYPE(*OBJOWN) function, but provides size, last used date, and text description also. A summary may also be made by either library or object type.
The Display Personal TAA Commands tool provides a menu of personal TAA commands such as DSPMONEY and DSPARACDE. The tool is intended for users who want personal as well as business functions.
The Display Program Adopt 2 command displays the programs which adopt (USRPRF = *OWNER) or those which do not use adopted authority from a calling program (ie CHGPGM has been used with USEADPAUT = *NO). Both *PGM and *SRVPGM object types are supported. The DSPPGMADP2 function operates on a library basis as opposed to the system DSPPGMADP command which operates on a user profile basis.
The Display Program Statement command is intended as a debugging aid when an error has occurred and the MI instruction number is known, but the HLL source sequence number is not. By entering the program name and the MI instruction number, DSPPGMSTMT displays a spooled file with the HLL source sequence number and statement. Only CLP and RPG OPM program types are supported. The source for the program must exist.
The Display Program 2 command displays or prints information about a program by combining information from DSPPGM, RTVOBJD, DSPPGMREF, DSPOBJAUT, the entry list parameters, and whether programs of the same name exist in any other libraries. Text descriptions are displayed for objects and users if they can be found. This simplifies searching for information about a program.
The Display Phone International command displays one, some, or all of the prefixes used for international calls. You may search by prefix or country abbreviation (such as POR). Only major cities are supported and many cities in English speaking countries.
The Display Prompted Command function prompts for a command and uses the returned string to 1) run the command via user specified QCMDEXC program, 2) parse the returned string into 68 byte blocks to be displayed, printed, sent to the job log, or written to a source member. Variables may be specified for the parameters of the command to be prompted for and will be filled at execution time. The variables must be declared in the program.
The Display Profile Authorizations command displays one, generic, or all profiles and flags those where the *PUBLIC or an authorized user has at least *USE rights to the user profile. The owner, *ALLOBJ users, and certain system profiles are bypassed. The user profiles that are flagged represent a security exposure as the *PUBLIC or authorized user can submit a job as the user profile or swap to the user profile.
Display Print Spacing. Displays spooled output with blank lines when extra spacing occurs. Displays skip information. DSPSPLF does not show any spacing or skipping information. Useful for determining what printed output formatting will look like without actually printing.
The Display PTF Save File Summary command provides a summary of save files for each release and product ID combination. This allows a review of how much space is being taken by PTF save files in QGPL.
Display Password. Provides a method of displaying a user’s password. The solution is to use the exit program specified for the security password checking program (QPWDVLDPGM system value) to capture the new passwords. The passwords are scrambled and stored in a data base file.
The Display Password Attributes command displays or prints the System Value password attributes. A description of the current value is provided on the interactive display along with help text. If the user has *SECADM and *ALLOBJ special authorities, a Function key allows access to the TAA CHGPWDA command prompt.
The Display Password Information command displays the information for one or more profiles relative to the password and signon information. The password itself is not displayed.
The Display Password Limit command uses converted data from QHST and displays or prints the devices and/or user profiles that have been disabled because the QMAXSIGN system value limit has been reached. This provides a good review of attempted break-ins or users who are having trouble.
The Display Password Limit 2 command uses converted data from QHST and displays or prints the conditions where a user profile has successfully signed on after one or more invalid password attempts to a list of user profiles. This provides a good review of authorized users who may be trying to discover a password of another profile.
The Display QHST command provides a method of searching the data from the QHST logs and displays or lists the entries. The QHST information must first be converted to a QHST2 file using the CVTQHST2 command. DSPQHST provides several search criteria such as a date range, a generic job or user name, message ID, and a scan value to scan the message text.
The Display QHST Inquiries command displays or lists inquiry messages and their replies from the QHST log. The formatting allows a better review than the DSPLOG command. A detail option for additional information is available.
The Display QHST Size command provides a simple listing with one line per QHSTxx file in QSYS and the total size. The date/time of the first and last message of each QHST version is also included along with the save date. This allows a review of QHST versions.
Display QHST 2. Provides an alternate method of looking at the messages that are sent to QHST. The CVTQHST2 command converts the messages to the QHST2 file in a named library. Logical files are built over this file to allow the quick access to messages using various key values. A subfile is used and the user can access the specifics of a message from an option. A MTNQHST2 command is provided to remove old messages from the QHST2 file.
The Display QMQRY command displays either a *QMQRY or *QRYDFN object by retrieving basic information about the object and the source retrieved by RTVQMQRY. The command may be useful in reviewing an existing query.
The Display Record Locks 2 command displays or prints the record locks held or waiting for a job. The system DSPRCDLCK command displays record locks for a physical file. DSPRCDLCK2 provides a simple means of checking in the same or a different job.
The Display RPG Call Parameters command displays the fields and their attributes that make up the parameter list for one or all Calls in RPG source. Externally described data and /COPY functions are supported. Useful for determining if the correct parameter list is being passed.
The Display RPG Count command counts the number of lines of code, array data, and comments in a source file. All RPG types are supported. A percentage of comments is provided. DSPRPGCNT provides a better understanding of the amount of actual source versus a count of the number of statements in a source member.
The Display RPG /COPY tool provides two commands. DSPRPGCPY provides a display or list of the /COPY and/or /INCLUDE statements from one or more RPG type source members (including RPGLE, RPGMOD etc.) in one or more source files. An outfile is optional which will allow further analysis by the DSPRPGCPY2 command which prints or lists the use of a specific member named on /COPY or /INCLUDE statements. A query may also be written.
The Display RPG Fields command displays the fields, their attributes and usage defined in an RPG source member. Options exist to display in field name order, by type and length, by usage, etc. The source may contain up to 1998 field definitions. Externally described data and /COPY functions are supported.
The Display RPG Help tool provides help text and samples for 1) RPG III operation codes and 2) RPG IV operation codes (both fixed and free form), Built-in functions, and H/F/D keywords. Help text may be displayed when using the Source Entry Utility (SEU) by entering ‘H’ or % in any column of the sequence number or by the command DSPRPGHLP.
Display RPG IGNDECERR Option. Displays the RPG create command parameter IGNDECERR. There is no system support (e.g. DSPPGM) to display this value on an existing RPG program. Debug is used to display the internal field ZIGNDECD. If it contains a ‘1’, IGNDECERR(*YES) was specified.
The Display RPG Call Parameters command displays the *ENTRY parameters that are used in RPG source. A simple one line per parameter listing occurs with the attributes of each parameter. Useful for determining if the correct parameter list is being passed.
The Display RPG Used command provides a method of displaying the programs that use an RPG field. The CRTRPGUSE command must be used first to create or refresh a data base file. DSPRPGUSE provides an indication of whether the program ‘uses’ or ‘changes’ each field. Both internally and externally defined fields are supported.
The Display Restore Date command displays or lists the objects that have been restored to a library after the library was restored. More than one library or the entire system may be reviewed. Options exist to list the new libraries and new objects (never restored). DSPRSTDAT assists in understanding what objects have been restored or created since the last restore of a library.
The Display Save Summary command displays or lists a save summary from one or more libraries of where objects are saved to. The objects are separated into several categories: 1) Not saved since created or changed 2) Saved to a save file or 3) Saved to a tape device. Separate summaries appear for each save file used and each volume ID (first volume only) used. A detail listing of objects is optional.
Display Save Tape. Shorthand command to DSPTAP for displaying the *SAVRST type labels from a tape. Minimizes keystrokes and need to prompt for the DATA parameter to display the Save/Restore information. Avoids the typical mistake of forgetting to specify DATA(*SAVRST).
The Display Submitted Jobs command provides a display that is similar to that provided by the system WRKSBMJOB command except that the user cannot perform actions against the jobs. An outfile is optional. An option exists to allow a display of any spooled files associated with the job. DSPSBMJOB may be helpful if you have a menu oriented system and want to prevent users from changing, holding, or ending batch jobs.
The Display Subsystem command provides a display for a single subsystem. High level information such as the status and number of active jobs are displayed. Up to 3 storage pools assigned to the subsystem are displayed and an option allows access to the storage pool statistics. Command keys exist to access the jobs that are active and the subsystem description.
The Display Subsystem Job Queue Entries command displays the job queue entries for one or more subsystems. This allows a review of the important entries that control batch work. Selection by a specific job queue may be made. An outfile is optional.
The Display Subsystem Jobs command provides a display that is similar to that provided by the system WRKSBSJOB command except that only a single subsystem may be displayed and the user cannot perform actions against the jobs. An option exists to allow a display of any spooled files associated with the job. DSPSBSJOB may be helpful if you have a menu oriented system and want to prevent users from changing, holding, or ending active jobs.
The Display Subsystem Job Queues command provides a display of the Job Queues specified for a subsystem and the jobs that are currently on the Job Queues. ‘Display only’ options exist. DSPSBSJOBQ provides a review of the batch work that is yet to be processed. See WRKSBSJOBQ for a ‘work’ version.
The Display Scheduled Job Queue Jobs command displays or lists the jobs on one or all job queues that have a scheduled date. A range of date and time value may be specified. You must have *ALLOBJ special authority to specify *ALL as a library qualifier.
Display Security Review. Provides a series of options to display or print the output from the DSPUSRPRF outfile. Different sequencing and selection criteria are available. Useful for security reviews in answering such questions as ‘Which users have *ALLOBJ authority’.
The Display Select Omit command displays or prints the select/omit criteria of a logical file. A better display exists than that used by DSPFD TYPE(*SELECT) which makes it more obvious what the relationships are. Only single format logical files are supported.
The Display Special Authority 2 command displays the combination of special authorities for a user, the group profile, and any supplemental group profiles. Selection can be made on the combined special authorities. DSPSPCAUT2 helps provide a better view of what an individual user can do.
The Display Spool Create Date command displays spooled files for one or more output queues in ascending create date sequence. Totals occur for each day. An outfile is optional. A beginning date may be specified to allow a number of current days to be bypassed. DSPSPLCRTD may assist in understanding cleanup requirements.
The Display Spooled File Attributes command displays or prints the attributes of a spooled file. The display is similar to the system WRKSPLFA display except that no changes can be made. DSPSPLFA is useful when a display is needed that does not allow the user to change any attributes.
The Display Spooled File Information command displays the number of spooled files for one or all users. DSPSPLFINF uses the RTVSPLFINF command to retrieve the information which uses the QSPSPLI API.
The Display Spooled File 2 command is is intended for users who operate from workstations which display 132 column mode. Because the font size can be difficult to read, some users may prefer to force an 80 wide display. DSPSPLF2 may also be useful on PC monitor devices due to the performance of changing the display between 80 and 132 mode.
The Display Spooled File 3 command is similar to the system DSPSPLF command, but allows heading information to be omitted on and after the first page. This can be helpful when displaying a spooled file where the page heading information causes clutter. An optional outfile allows you to output a spooled file to a ‘headingless’ data base file to allow processing by a program.
The Display Spooled File 4 command is designed to be used with WRKALLSPLF. It allows the spooled file to be displayed and then a prompt appears which allows a response of retain, delete, or re-display. This allows the user to request to see several spooled files and delete those required without returning to the main display and attempting to remember what to delete.
The Display Spooled File 80 command displays a spooled file in an 80 wide display format even though the display is capable of a wider width (such as 132). This provides for a larger font size when viewing spooled output. The same windowing, paging, and ‘find’ functions as exist for the system DSPSPLF command are supported. Blank lines may be excluded (same as DSPSPLF) or included.
The Display Spooled Files Owner command displays or lists by spooled file owner either each owned spooled file or a summary by user. This allows a review of how many spooled files and how much spooled file storage is owned by users. Specific libraries may be named or all libraries.
The Display Spool Size command displays the number of members and their size from the QSPL library. The number of members with and without data are also displayed. A member may exist that does not hold any spooled data as the system tries to limit the number of members that must be created.
The Display Spooled File Use command displays spooled files from one, generic, or all output queues that have not been used in a specified number of days. This provides an assist in cleanup where users claim they need spooled files kept online. The DLTOLDSPLF command may be used to clean up old spooled files that are not being used. See the COMPDATE parameter.
The Display Source Change command displays the changes to a source member between two dates. Both dates default to the last time the source member was changed. The default is to display just the changes. All statements may be listed with the changes flagged.
Display Source List. A subfile approach for looking at source member level information. The supplied command CPYSRCLST refreshes the file used. CPYSRCLST should be run on a regular basis. DSPSRCLST allows access by member name or by library/file/member. The source member names can be scanned as well as the text when attempting to determine a source member name. Provides a faster solution than DSPFD member list or PDM.
Display Source Member. Provides a display of source whether the Application Development Tools (including STRSEU command) are on the system or not. If STRSEU does not exist, DSPPFM is used. Useful for those situations where code is to run on a different system and you don’t know if the STRSEU command exists.
The Display Source Members command displays or prints source member information from one or more source files with various selection criteria. The selection options include source type, generic member name, create date, change date, last used date, a scan of the member name or text, and the number of existing records. DSPSRCMBRS simplifies searching for source member information.
The Display Source Member 2 command provides a similar display to STRSEU SRCMBR(*SELECT), but only display or print options exist. The user cannot delete or edit a member. The display of the source may be done using either STRSEU (browse mode) or DSPPFM.
The Display Source Type tool displays the standard source types used by the system and a text description for each.
The Display Storage Pool command displays or prints the attributes and performance statistics of a storage pool. Either a shared pool name (such as *BASE) or a system pool ID may be specified. The display may be refreshed and the performance statistics reset.
The Display Storage Use command displays or lists the amount of storage used in descending order by user profile. A percentage (default of 90%) may be specified to flag those profiles that are approaching the maximum storage allowed per profile. DSPSTGUSE is helpful in understanding what users have used versus the maximum allowed for each.
The Display Summary of Job Queue command provides a summary of a job queue by Status and Job Priority. One or both of the summaries may be listed along with an optional line for each job. DSPSUMJOBQ can help determine how many jobs exist for each type.
The Display Summary of Output Queue command provides a summary of an output queue by Status, Form Type, and User Data. One or all of the summaries may be listed along with an optional line for each spooled file. DSPSUMOUTQ can help determine how much printing must occur for each type.
Display System. Displays the important characteristics about the system such as the name, serial number, model, release ID, disk capacity, system ASP percentage used, security level, TAAUPDATE date, etc. Useful for those people who signon to multiple systems as a refresher.
The Display System Partitions command displays information about the current system partition and a summary of all system partitions.
The Display System Security command displays or lists the high level information about system security and what the pending changes are. The RTVSYSSEC TAA command is used to retrieve the information.
The Display System Value Attributes command provides a more convenient manner of determining the attributes of a system value for RTVSYSVAL than the RTVSYSVAL help text. A simple display appears with the attributes and the group that the system value exists in.
The Display TAA Categories command displays a subfile of tools in a category such as *SPL or *SRC. After you select a tool, a display provides options for displaying the member heading information and displaying/printing of the tool description. Options on DSPTAACAT assist you in finding the correct category.
Display TAA Commands. The TAA commands are displayed in a subfile. Options on the command allow the subfile to be displayed with the first value entered (e.g. show all of the commands which begin with EDT). A scan capability also exists to show all the commands that have a specified string within the command name or the text. Useful for determining which command to use when you do not know the full command name.
The Display TAA Integration Date command displays or lists tools by integration date. This provides a review of what tools have been shipped by date. A ‘from’ and ‘to’ date may be specified along with a category. A count by year is optional.
The Display TAA License command provides a simple method of reviewing the important characteristics about the license for the TAA Productivity Tools and installation information. It also provides access to the TAALICENSE and TAACTL data areas.
Display a TAA Member. This is a shorthand to SEU browse mode with the library defaulting to TAATOOL. It provides a simple keystroke method of looking at TAATOOL source.
The Display TAA Name command allows input of 4 characters for a TAA ID such as SRCF and sends a completion message with the tool name and description. This can simplify determining what tool is being used when only an object name is known.
Display TAA Tool. Displays the text information associated with a specific TAA tool. The QATTINFO file in TAATOOL must exist. A single tool or all of the tools may be printed. Printing all of the tools produces a great deal of spooled output.
The Display Tape Label command displays or prints basic information about a tape label including the date the first file was written and the first expiration date. DSPTAPLBL is very efficient in displaying information from a virtual tape. The command can be very slow when certain tape devices exist.
The Display Tape Size command displays or lists an approximation of how much data has been written to a tape. Each file is listed along with a total. An outfile is optional. Hardware compression is not considered. DSPTAP is used to determine the information. Because a spooled file must be read, only lower and upper case English is supported.
The Display Tape Volume command provides a simple fast method of identifying the volume label of a mounted tape. A display appears with the name of the volume. Function keys allow either the use of DSPTAP or the TAA DSPSAVTAP command.
The Display Table command is similar to the display that appears using option 5 from the system WRKTBL command to display a *TBL object. A listing is optional. The TAA version also shows any differences from the base value. For example, if X’04’ is output as X’37’ and not as X’04’, ** is used to flag the position.
The Display Time Adjustment command displays the information regarding a time adjustment. See the TAA command ADJTIM for a method of changing the time of day clock forward or backward n seconds. DSPTIMADJ displays the information of whether an adjustment is being made and if so how much time is needed to complete the adjustment. The RTVTIMADJ command is also included which uses the QWCRTVTM API.
The Display Time Formats command displays the valid time formats for data base ‘T’ type fields. Examples of each TIMFMT option are shown. The ‘Z’ type Timestamp field is also described.
The Display Time Zone command allows you to display the time difference between major cities throughout the world. This provides a simple solution for determining the local time in a different part of the world.
The Display Time Zone Time command displays or lists the date and time for a specified time zone. The day of week and offset from GMT are also shown. Daylight savings time (DST) is considered if the time zone supports DST and the current date/time is within the DST start and end date/time.
The Display Temperature command provides an interactive display to assist in converting from Fahrenheit to Celsius or from Celsius to Fahrenheit.
Display Tool Command. Provides a method of displaying the commands associated with a tool. A subfile is used to display the commands and an option exists to prompt for the command. A function key allows access to the tool documentation. If the name entered is not a tool but is a TAA command name, the tool name is determined and the subfile appears as if requested by the tool name.
The Display Total Pages command displays or lists a running total of the pages for spooled files in an output queue. The intent of the command is to provide an indication for a user of where his output is in the queue and how many pages are to be printed before a specific spooled file.
The Display Trigger Status command displays the trigger status of the programs for one or more files in one or more libraries. An ‘escape’ parameter exists to allow you to send an escape message if one or more programs are disabled or inoperative.
The Display Text tool simulates (as best it can) a PC browser function on an i5 System. The data to be displayed is passed in an array of up to 9,999 elements of 78 bytes each. You must supply a program to interface to the Display Text tool. Use the DMODSPTXT command for a demonstration.
The Display Text Count command is designed for an analysis of TXT type members in a source file, but may be used on any source type. One, generic, or all members in a source file may be analyzed. Total records and blank records are always counted. Up to 5 comparison groups (such as all the ABC values in a From/To location within a source record) may also be compared for an equal value or scanned for a value.
The Display UIM Count command counts the number of lines in one or more members containing UIM type source. Source types in addition to PNLGRP may be specified. Comment lines and blank lines are also counted. A percentage of comments is provided. DSPUIMCNT provides a better understanding of the amount of actual source versus a count of the number of statements in a source member.
The Display Unique Key command displays the number of unique values in the access path fields for a data keyed file (non source). The file does not have to have unique keys. The system provides the number of unique values for the first 4 key fields of a file. This means a count of the unique values for key 1, key 1-2, key 1-3, and key 1-4. One line is listed for each member. The information can provide a better understanding of the data.
The Display Unique Key Totals command displays or lists members in one or more data files in a library. The number of unique keys for the first 4 keys of each keyed access path are listed. This can provide a better understanding of the data that makes up the keys of the file.
The Display USA History command displays information about the history of the USA by year. This includes notable events such as Presidential elections, significant battles, and other information. Some major events outside of the US are also included.
The Display USA President command displays information about a US President including the electoral voting, the Vice President, notable cabinet members, and major events that occurred during the presidency. By default a list of Presidents will be displayed and a selection may be made (F19) or a specific President may be entered on the command.
The Display User Auditing command displays a list of users and the attribute information about object auditing. A single user, a generic name, or all users may be requested. You may optionally bypass any user who does not have user auditing requested.
Display User Authority. Allows for an authorization review by combining the authorities from the individual object, authorization list, and group profiles. In a complex authorization structure, it is difficult to determine who can do what. Provides answers to questions such as ‘Who can update an object?’, ‘What can USERA do in LIBX?’, ‘What can the public do in LIBY?’. Identifies any private authority that is less than the public authority.
The Display User Authority 2 command displays a user’s authority to objects within a library. Both individual authority, group authority (including supplemental groups), and authority controlled by authorization lists are described. An individual object, a generic name, or all objects can be specified. A specific type, or all object types may be requested.
The Display User Authority 3 command displays or lists the authorities that have been granted to a specific user for one, generic, or all objects. A specific object type may be named. Inclusion of the user’s owned objects is an option. DSPUSRAUT3 provides a better review than DSPUSRPRF.
The Display User Authority 4 command lists all objects in a library that a named user is not authorized properly to. For example, if the user should have *CHANGE authority to all objects in the library, a line would be listed for each object where the user has 1) no authority 2) is specified as *EXCLUDE, or 3) has only *USE authority.
The Display User Commands command displays the audit records for commands run by a user that is specified with CHGUSRAUD AUDLVL(*CMD). DSPUSRCMD is intended for use on critical security profiles such as QSECOFR and QSRV to allow a review of the commands that were entered. The Journal Code T (Audit) records with an Entry Type of CD (command was run) are processed using the CPYAUDJRNE outfile.
The Display User Index Entries command displays or prints the entries in a user index object. Only fixed length keyed user indexes are supported up to a 2000 byte maximum entry length. The initial display shows one line per entry and allows positioning to a key. A detail display is available with an option to display in hex.
The Display User Index Attributes command displays or prints the attributes of a user index. Any user index may be specified (not just those created by the TAA CRTUSRIDX command).
The Display User Job command is a display only version of the system WRKUSRJOB command. Only display options are valid for a job. An option exists to display, work with, or prevent access to the spooled files of a job. Any user can display jobs and display the details of his own job. Only a user with *JOBCTL special authority or with authorization to the TAAJOBCTL authorization list can display a job which is not his own.
Display User Profile 2. Provides a simple solution for Assistant Security Officers to be able to display any user profile. Controlled by the TAADSPUSR2 authorization list. Also found on the SECOFR2 tool menu.
The Display User Signon command displays the hours and minutes that one or more users were signed on. The JOBACG tool is required and the latest job information must be converted from the QACGJRN journal. The default option lists each signon by a user (from any device) with day and user totals for the days requested. You may request a day total or just a user total.
Display User Space. Displays the contents of a user space. The first 400 bytes of the user space are displayed in both character and hex. An option exists to display 1200 more. Useful for debugging and as an education aid to understand what is in the user space.
The Display User Space Attributes command displays or prints the attributes of a user space. This includes the internal size, the auto-extend option, and the initial value.
The Display User Storage command provides a display or listing with one line per user of the number of objects owned and the total storage used. One, generic, or all users may be requested along with an omit list. The number of programs, files, and other objects is also shown.
The Display User Text command displays a user text description based on a user profile name. The command is useful if additional information is stored in the text description of the user profile. The user of the command does not need to be authorized to the user profile. Only the text description is displayed.
The Display Virtual Tape Resources command provides a subfile display of the virtual tape resources. The command must be entered in an interactive environment. To see the virtual tape resources that are in use, enter the DSPVTP command.
Display Where Used. Provides a method of viewing the output from DSPPGMREF in a subfile by referenced object. This allows a simple means of displaying an object and determining the using programs. An option exists to add *QRYDFN and *QMQRY objects. A detail display describes both the object and the using program in more detail.
The Display Window command displays a window over the current display. The intent of the command is to provide for a better informational display in exception conditions. Ten lines of text may be presented plus an error line. The command ends normally if the user presses Enter, F3, or F12. A single F key (such as F4 - F24) may be defined with user supplied text.
The Display Wind Chill command displays a table of ‘Wind speed per hour’ and ‘Fahrenheit temperature’ (or Celsius) to describe the wind chill effect.
The Display Writer command is similar to the system WRKWTR command, but allows only display options plus describing the number of files in the associated output queue. The command is intended for end users who need to display information about one or more writers, but should not be able to make any changes. An optional method of displaying the output queue associated with the printer is provided.
The Display Writer Status command displays the status of a writer. The printer device name must be entered. No change options are supported. This allows typical end users to determine the writer status without providing options to change.
The Data Area Archive provides online save files for specified data areas. Multiple versions may exist for each data area. The DTAARAARC tool is not intended to replace normal backup, but rather to allow a quick review of a previous value. A typical use would be to restore the object to a different library to allow a review. You can also restore from the online save files. Several commands are provided.
The Data Archive provides online save files for critical data. Multiple version may exist. Options exist for ‘save while active’ and saving dependent logical files. The DTAARC tool is not intended to replace normal backup. A typical use would be to restore the save file to a different library to review a previous value. In an emergency, you can restore from the online save files.
The Duplicate All Spooled Files command duplicates selected spooled files from one output queue to another. The default is to duplicate all spooled files. A variety of selection criteria exists.
The Duplicate Authority command duplicates the authority from one object to another. Any existing authorities for the To object are removed first. The authorization list and existing authorities are made identical. An option exists for who the owner should be and his rights to the To object. Program adoption is not considered.
The Duplicate Authorization List Authorities command duplicates the authorities from one *AUTL to another. Both *AUTL objects must be owned by the same user. All authorities from the To *AUTL are removed first and the authorities from the From *AUTL are copied. DUPAUTLAUT is helpful when you want to create an *AUTL that is similar, but not the same as an existing *AUTL.
The Duplicate Characters command duplicates a string of 1 to 50 characters to a return variable. An output length must be described. The return variable must be 32,000 bytes. DUPCHAR can be used as a testing aid or for other unique situations.
The Duplicate Changed Objects command is intended for the case where you are maintaining an application on one system and need to keep a duplicate of the application up to date on another system. DUPCHGOBJ lets you capture the changed objects (including data base networks) and places them in a separate library. A tool such as MRGOBJ could then be used on the target system to merge in the changed objects.
The Duplicate Command and Source command allows a command and its source to be duplicated from one library to another. This is useful when commands and their corresponding source must be transferred.
Duplicate physical file and dependent logicals. Duplicates one or more physical files from one library to another as well as any dependent logical files. No data is copied. Useful for changing data base definitions by creating the same network in a separate library.
The Duplicate Display File and Source command allows a display file and its source to be duplicated from one library to another. This is useful when display files and their corresponding source must be transferred.
The Duplicate File Format command duplicates a file using the same format as a specified file. The new file will not have any keys (i.e. it is arrival sequence). A physical or logical (with a single format) including a join file may be duplicated.
The Duplicate File Format 2 command duplicates a file from a physical file to a new file with the same format as the original file. The user must have *USE rights to the file being duplicated. This differs from CRTDUPOBJ which requires *OBJMGT authority.
The Duplicate Job Spooled File command duplicates the spooled files for the current job to a different output queue with a different owner. This allows a tool like Spool Archive (SPLARC) to back up a job’s spooled files even if the owner deletes them when the job completes.
Duplicate Message Description. Duplicates a message from a specified message file to the same or another file. Useful when you want to create a message based on an existing message description.
The Duplicate Program and Source command allows a program and its source to be duplicated from one library to another. This is useful when programs and their corresponding source must be transferred.
Duplicate Spooled File. Allows a spooled file to be duplicated to a different output queue. Uses an API. No restrictions exist. The DUPSPLF2 command provides different capability as it does the copy using CPYSPLF and CPYF. Useful for making copies of spool files.
Duplicate Source Member. Provides a front end to the CPYSRCF command to make it easier to duplicate a source member. The defaults and special values provide a simpler interface.
Duplicate Standard Source. Duplicates skeleton source for the typical source types. This simplifies the beginning of a new source member as many typically used functions are already coded. A text description can be added using the command prompt and will also appear as part of the first source record. The standard source can be modified for individual requirements.
Duplicate TAA Commands. Provides a method of duplicating commands and other objects from the TAATOOL library to a command library. The concept of a command library is described in the information member “Library List Requirements” on the HELPTAA menu. The companion tool is DLTTAACMD.
The Duplicate TAA Data Base File command is an internal tool that is used to duplicate certain files from TAATOOL when a CVTxxx TAA command is used. The command is not intended to be used by users except within the CVT programs. The purpose of the tool is to allow files in TAATOOL to be *PUBLIC *USE and still allow the file to be duplicated. The program adopts QSECOFR authority.
Duplicate a Tape Using a Single Tape Device. The tape is read in by the DUPTAPIN command and written to a data base file. The DUPTAPOUT command can then be used to create a duplicate to the same device. Multi-volume tapes are supported. A significant amount of storage is needed to hold a tape. For example, the system distribution tape will require approximately 500 MB of DASD storage for V2R3.
Dynamic Menu. Provides a method of writing menus where the options on the menus are driven from data base records. An option on a menu can cause a command or a sub-menu. Many additional functions exist such as an optional command line, authorization of options, review of current use by user, historical review, and the ability to easily turn any menu or option into a Group Job. A demonstration program exists.
The Edit Authorization List 2 command is designed for the case where many users exist on an authorization list and it is desirable to display the users in name sequence. This is as opposed to the system EDTAUTL command which displays the users in user profile create date sequence. An exit program may also be named to pass any changes to other systems.
The Edit Data Base File tool provides a simple means of displaying or maintaining a data base. A physical file or a logical file with a single format may be processed. The EDTDBF command allows records to be displayed, changed, added, or deleted. The DSPDBF2 command provides a ‘display only’ function.
Edit Data Area. Places the current value of the data area into the prompt for the CHGDTAARA command. Uses the API QWCRDTAA. Useful for any changes to data areas. See also the EDTDTAARA2 tool.
Edit Data Area 2. Provides an alternative method of editing the existing contents of a data area than the TAA Tool EDTDTAARA. EDTDTAARA2 uses a display that is similar to DSPDTAARA where each line of 50 bytes is a separate field. EDTDTAARA considers the entire data area to be a single field on the display.
The Edit Data Area 3 (Hex) command provides an interactive display to change the value of a data area in Hex. Both the Hex and EBCDIC values are displayed. Only type *CHAR data areas may be specified. The command may only be used in an interactive environment.
The Edit Data Queue command allows editing of character data in a non-keyed data queue with a maximum entry length of up to 5000 bytes. An interactive display is used for editing and updates, deletions and new entries may be made.
Edit Job Description. Places the current value of the job description into the prompt for the CHGJOBD command instead of *SAME. A separate command (EDTJOBDLIB) is provided to edit the library list within a job description in a manner similar to the EDTLIBL command. The system support of CHGJOBD provides a similar function. For the library list function, EDTJOBDLIB may still be preferred.
The Edit Large Variable command provides editing for a large character variable that contains numeric data. Some system functions return large character variables that exceed 15 digits and place them in *CHAR variables. A *CHAR input value of up to 30 bytes is supported. The return CHROUT value must be declared as *CHAR LEN(43).
Edit Network Attributes. Places the current value of a specified network attribute into the CHGNETA command prompt instead of *SAME. Useful for changing network attributes.
The Edit Object Authority 2 command is similar to the system supplied EDTOBJAUT command except that the names appear in alphabetical sequence following the owner and *PUBLIC user. A ‘position to’ option exists. An option exists to capture the GRT/RVK changes so they may be logged or sent to another system.
The Edit Source tool is a subset of an SEU (PDM) like function. The intent of the tool is to provide a simple source editor for a system that does not have the STRSEU command or a similar function. This would be typical in some remote or small installations. Any source may be edited, but prompting exists only for CLP, CLLE, and CMD type source.
Edit User Profile. Similar to CHGUSRPRF in that it allows changing of an existing profile using the current values displayed in the CHGUSRPRF prompt. EDTUSRPRF provides a simple method of capturing the executed CHGUSRPRF command in a journal. The journal or journal entry can be sent to another system and the same command executed there. Useful for keeping multiple systems in synch when making user profile changes.
The Edit User Space command allows data to be written or changed in a user space. An option on the command allows editing in character or hex mode. EDTUSRSPC provides a convenient method of storing and maintaining data in a user space object or making changes when data is written to a user space by another function.
Edit Variable. Allows a decimal CL variable to be edited into a character field. Useful for converting decimal values into a form that is meaningful for messages. The command strips off leading zeros and inserts an optional decimal point. Most RPG edit codes may be specified. Useful for CL applications which need to convert packed decimal values into readable values.
The Edit Variable 2 command is an enhanced version of the existing EDTVAR tool. The EDTVAR2 command provides more Edit Codes and options. EDTVAR2 may be used as 1) A command in a CL program, 2) A sub program that can be called, or 3) A subroutine within an RPG program. A maximum of 15 digits is provided for. A testing command (DMOEDTVAR2) is provided.
The Edit Variable 3 tool is like EDTVAR2, but allows editing of up to 30 digits. EDTVAR3 may be used as 1) A sub program that can be called, or 2) A subroutine within an RPG program. A testing command (DMOEDTVAR3) is provided.
The Enable Group Profile command ensures that all members of a group profile are enabled. The companion command is Disable Group Profile which ensures that all members of a group profile are disabled. An option exists to determine if the users who are part of a supplemental group profile should be enabled/disabled. No change to the status of the named group profile occurs.
Enable User Profile. A user profile is normally disabled by exceeding the number of password attempts and the setting of the QMAXSGNACN system value. ENAUSRPRF changes the profile back to an enabled state. The command adopts the security officers authority and is intended for use by trusted personnel. The user of the command must be authorized to the TAAENAUSR authorization list.
The End Active Job command ends jobs for a specific job name, a user name, or both. All batch and interactive jobs would be ended. Jobs on the job queue would not be ended.
The End Disconnected Job command checks for jobs in the DSC (disconnected) state and ends them by default. This allows a simple cleanup solution prior to a backup. An option exists to just list those jobs that are in the disconnected state.
End Duplicate Jobs. Allows all jobs to be ended even if duplicate names exist. ENDJOB supports the ADLINTJOBS parameter to allow the ending of all interactive jobs. ENDDUPJOB will end both interactive and batch jobs.
The End Interactive Jobs command ends all interactive jobs except the current job and those found on omit lists of devices and users (see the Omit list discussion). Selection by subsystem and generic user can be made. The command may be used in conjunction with the SNDINTMSG command which can inform users a few minutes before ending their jobs.
The End Jobs With Object Locks command ends all batch and interactive jobs holding locks on a specified object.
The End Job 2 command provides for ending multiple jobs such as generic job names, generic user names, etc. The parameters of the command (such as OPTION and DELAY) are passed to individual ENDJOB commands for active jobs that meet the selection criteria. You must have *JOBCTL special authority to use ENDJOB2.
The End Old Job Queue Jobs command ends jobs which are on one or all job queues based on a specified number of retention days. Jobs that have a schedule date are bypassed. An Action parameter exists that allows a determination of the jobs that would be ended if ACTION(*END) had been specified.
The End Subsystem Job command ends one or more jobs from one or all subsystems based on a number of minutes active. For example, you can end all jobs in a subsystem that have been active for more than 640 minutes (8 hours).
The End Subsystem 2 command is similar to the system ENDSBS command except ENDSBS2 does not complete until the subsystem has reached an inactive state. Wait time options may be specified. ENDSBS2 simplifies writing a CL program that ensures a subsystem has ended properly.
The End Subsystem 3 command will quiesce a system, but not take the system completely to restricted state. All subsystems will be ended, except QCMN, QHTTPSVR, QSERVER, QSPL, QSYSWRK, QUSRWRK, TAAUPSMON, the controlling subsystem, and those specified in the OMIT parameter.
End TAA License. Provides a method of terminating the license to the TAA Productivity Tools by placing an expiration date of 90 days from the current date in the TAALICENSE data area. Useful for the case where the license is being terminated or the license is being transferred to a different serial number.
Execute Commands from a Source Member. Allows an inline execution of commands instead of submitting a job to batch. Useful when you have entered several commands interactively and then want to execute them again. You would achieve this by using the TAA tool CPYJOBLOG command to copy the commands to a source member and then use EXCCMD.
Execute Command Check. Provides a method of allowing a command to be entered by a user (with optional prompting) and returns the string to be executed with keywords included. Like QCMDCHK except that keywords are added to the string. Intended for use in an application where the command will be stored in a data base and executed at a later time.
The Execute using *JOBCTL command is intended for the situation where the user needs *JOBCTL authority, but should not be permanently authorized. Specific TAA functions are supported and the Security Officer may authorize other commands. The user must be authorized to the TAAJOBCTL authorization list.
The Execute OUTPUT parameter command is designed for use by user written DSP commands which support a standard OUTPUT parameter (defaults to * and allows *PRINT). EXCOUTPUT provides either DSPSPLF or RLSSPLF depending on the job type and the value of the OUTPUT parameter.
Execute Source. Executes source in a source member based on a label identification on a source statement. Generally used for object creation where the CRT function requires specific parameters or multiple commands. Allows variable substitution for such functions as the source file, the source file library, the object library, etc. Can be executed from PDM with a user defined option. Useful for consistent object creation.
The Expire File tool is a series of commands that allow you to set an expiration date for a file of any type. The system supports an expiration date for members, but not for files. You must have *ALLOBJ authority to use any of the commands in the EXPFIL tool.
Expand Value. Provides a solution for the situation where a RTV command returns a list of values in a single variable that may not have a space between the values and you want to use the list in QCMDEXC.
Expand Volume ID. Takes a four character volume ID (e.g. ABCD) and expands it to 50 volume ID names (e.g. ABCD01, ABCD02 … ABCD50). Useful for save/restore operations to assist the operator in mounting the correct volumes in sequence. The save/restore function will require the tapes to be mounted according to the volume ID list, but will not require the full list to be mounted. Must execute thru QCMDEXC.
Extract Command. Extracts a command and the command library (if any) from a string. Useful for determining which command was entered when the user enters a command in a string form. The string could be entered interactively or it could be passed by a program which is reading source.
Extract List. Extracts an entry from a list passed from a command parameter. Useful for creating commands which allow lists for parameters. Simplifies the coding in the command processing routine.
The Extract List 2 command is intended for the case where a CL program is the CPP for a command which uses a list and the list must be passed to another command or to a HLL program. Because of the way the list is passed by command processing, garbage may appear in the positions where the user did not enter a value. EXTLST2 cleans up the list so it may be passed on.
The Extract List 3 command accepts input from a simple list parameter passed from a command and returns a value that is suitable to be moved to a variable for listing or displaying in a message. One space would exist between each value returned. The command would typically be part of a CPP that needs to make the list displayable and not as it is passed to the program.
The Extract Qualified Job Name command accepts an input value such as ‘123456/USERA/JOB1’ and returns separate variables for JOB, USER, and JOBNBR. If your program is attempting to parse a message containing a qualified job name, EXTQLFJOB may be helpful.
The Extract Qualified Name command extracts an object and optional library qualifier from a string such as ‘ABC/DEF’ where ABC is considered to be the library and DEF the object. Leading blanks and apostrophes are ignored. Any characters following the end of the object name (after the blank delimiter) are ignored.
The Extract Value command extracts the value from a character variable. If the value is surrounded by quotes, the quotes are removed. The command may be helpful when dealing with spooled printed values.
The Favorite Command tool provides a simple method of executing your favorite commands. Your favorite commands would be placed in a data base file by either a Work function or an Add command. The Add command extracts the previous command from the current program message queue. A unique name must be assigned to each favorite command. A favorite command is then executed by either a special command or from a display.
File Feedback Definition. Provides data structure definitions for the RPG file feedback area. Can also be used by other HLLs. Useful for dealing with the file feedback area as it provides standard definitions and avoids errors when adding offsets.
Find Generic Objects. Finds all generic objects in the current library or first library on library list with minimal keystrokes. Front end to WRKOBJ, but faster for accessing a normal request.
The Find 2 command is intended to assist you in identifying all the objects of a generic name on the library list, in a specific library, all libraries, etc. Messages are returned when an object is found.
The Fix All Source command provides a method of making mass changes to member data in a source file based on a ‘From value’ found in the source. Any type of source is valid to be changed. Because ACTION(*CHECK) is the default, no changes will be made allowing a review of what would be made by ACTION(*CHANGE).
The Fix CL ENDDO command adds a comment to the ENDDO commands in CL source that matches the expression such as (&A *EQ &B) of the corresponding IF command. MONMSG commands with EXEC(DO) are handled in a similar manner with the message ID added as a comment to the corresponding ENDDO. One, generic, or all CL and CLLE source members in a source file may be specified.
Fix CLP Source. Provides a method of adding keywords to CLP, CLLE, or CMD type source using a command. The result is similar to if you had used the prompter in SEU on every command. The command also provides a solution of converting source from one size source file (e.g. 92 bytes) to a larger size and utilizing the extra length.
The Fix Data Base Field changes a character field (or an entire record) in a member to trim leading blanks, remove specified characters, and translate characters. A single field may be used for selection. FIXDBFFLD may be useful when data is received from another system that contains unwanted characters.
The Fix Decimal Errors command fixes packed and/or zoned fields in an externally described file member. Packed fields are set to zeros if invalid decimal data exists. Zoned fields with invalid characters have the characters made valid. Use the VALDBF tool to check for decimal errors (does not change values).
Fix Help Record. Modifies the DDS source associated with the DMOSUBF tool to allow the help formats to be moved to a different file.
The Fix Minimum Release command finds objects that were created with a target release earlier than the one specified on the command and replaces the object for most cases. *PGM, *MODULE, and *SRVPGM objects are checked. *MODULE and single module *PGM objects are replaced. Objects with creation data may be bypassed. All *SQLPKG objects are flagged. The tool is designed to assist in conversion to V6R1M0.
The Fix Qualified CPP command is intended to library qualify the programs that are called from the command definition object of user written commands. This is an important consideration if you write programs that adopt (USRPRF = *OWNER). A command definition object (*CMD) describes the CPP and its library. If the CPP uses *LIBL or *CURLIB,
The Fix Qualified Name command allows you to add a library qualifier to non-system commands (and optionally to system commands) used within CL source. The source is updated to include the library that the command is found in. The source is reformatted in a manner similar to if you had prompted for every command in SEU. The library of the command must be on the library list and the first occurrence is used.
Fix RPG END Operation Codes. An RPG member or all RPG members in a file can be read to determine if any END statements should be changed to the appropriate ENDIF, ENDDO, ENDSL, etc. The default is to change the statements. An option exists to check the source only. Useful for cleaning up source to use the more explicit END operation codes.
The Fix Source Date command checks for invalid dates in the SRCDAT field of source members. Only the YYMMDD format should exist. A single member, generic members, or all members can be checked in one or all files in a library. A listing occurs of any invalid dates. An update option exists to to change the dates to valid dates.
The Fix Source Sequence Numbers command searches for invalid decimal data in the sequence number positions (1-6) of source statements. The default prints a report of any statements that have invalid decimal data. An option allows updating to create valid sequence numbers.
The Fix Variable command allows an input variable to be changed by replacing a character with one or more characters (up to 10) or deleting a character. The new value is returned in a 5000 byte variable. The input variable may be up to 5000 bytes, but a length should be specified to improve performance.
Format line. Provides a solution for formatting a string of text so that a word is never split over a line and excess blanks are squeezed out. A return variable provides the formatted text. Special formatting options allow control over when a new line occurs, line indentation, and blank spaces within a line.
The Format Options tool provides an assist when several lines are required to describe options or command keys in a typical subfile application. For example, on the WRKMBRPDM display there are two lines for option descriptions and two lines for command key descriptions. However, there are more options and command keys than fit in two lines. Generating the proper display lines is simplified by the use of FMTOPT.
The Format Qualified Command command allows CL source to be formatted so any qualified commands begin in position 14 of the source with the command name. The / is placed in position 13 and the library name to the left. This aligns the command names for easier reading of the source. The command prompter formats a qualified name so the library name begins in position 14.
The Find Command command displays a list of commands that match a string such as ‘JOBD’. By default all commands from QSYS and TAATOOL are displayed that match the string. When the display appears, options exist to prompt for the command or use the TAA DSPOBJD2 command. A separate command CRTFNDCMD may be used to build the file of commands for all or named libraries.
The Find Command Text command displays or prints a list of commands that match a string somewhere in the text description of command objects such as ‘printer’. A file of commands is created by the TAA install process (using the FNDCMD tool) which contains all commands on the system except for duplicates in QSYS and the previous release libraries.
The Find Job command provides an interactive display of jobs by entering job/user/status values. The job and user names may be generic and may contain wildcards. Options exist on the display for further information or for actions such as ENDJOB if authorized. FNDJOB simplifies finding a job when only part of the job name or user name is known.
Find Message ID finds the message file(s) that hold a message ID. This is very useful when handling jobs which list a message id with and unknown message file. The product issuing the message can often be identified this way.
The Find Object Member command attempts to match the source member name used to create an object with a source member in one or more source files. This is designed for the case where the source has been moved or duplicates exist for the same member name. One or more objects may be specified with one or more libraries checked for where the source may exist.
The Find Object Name command searches for an object name, a generic object name, or a string of characters in a object name. A single object type or all object types may be searched. A single library, multiple libraries, or all libraries may be searched. Either messages are sent or a spooled file is output.
The Find Object Text command searches for a string of characters in the object descriptions in a single library, multiple libraries, or all libraries. Either messages are sent or a spooled file is output. The intent of FNDOBJTXT is to assist you when you cannot remember the object name, but you do remember some string of characters in the object text.
The Find Renamed Restore File command outputs a spooled file for any files found that have a name ending in 4 digits. This typically occurs if a file has been saved, the format of the file has been changed, and you have requested a restore of the original object with ALWOBJDIF(*ALL). One or more libraries may be searched. FNDRNMRSTF can assist you in cleaning up your system.
The Find Renamed Restore Members command outputs a spooled file for any members found that have a name ending in 4 digits. This typically occurs if a member has been saved, deleted, re-created with the same name, and then restored. One or more libraries may be searched. FNDRNMRSTM can assist you in cleaning up your system.
The Find Spooled File command can assist when you are trying to find a spooled file, but you are not sure of the name, the job, the form type, etc. FNDSPLF allows you to identify one, generic, or all output queues that should be searched for whatever information you have such as the form type or some string of characters within the form type. Most of the selection options supported by FNDSPLF allow this type of searching.
The Find Source Member command searches for a member name, a generic member name, or a string of characters in a member name. A single source file or all source files in a single library, multiple libraries, or all libraries may be searched. Either messages are sent or a spooled file is output. FNDSRCMBR assist when you cannot remember the full member name or where it exists.
The Find Source Text command searches for a string of characters in the text description of source members. A single source file or all source files in a single library, multiple libraries, or all libraries may be searched. Either messages are sent or a spooled file is output. The intent of FNDSRCTXT is to assist you when you cannot remember the source member name, but you do remember some string of characters in the member text description.
The Find User Attribute command finds objects that have a named user attribute or any user attribute. A listing is displayed or output. User attributes allow a further identification of objects.
The Find Word command lets you find an English word beginning or ending with the letters you specify or you may scan for all words containing the value that was entered. Wildcards (’_‘) may also be used. An option exists to include proper names such as ’John’ and place names such as ‘Johnstown’. The supplied dictionary that is searched has about 80,000 words and names. FNDWRD is helpful when you do not know how to spell a word or name.
The Force Object Storage command forces an object in the *USER domain to non-volatile storage. Only the object types *USRIDX, *USRQ, and *USRSPC may be specified and the object must be in the *USER domain. Without forcing the object to non-volatile storage (disk), a system failure could cause the object on disk to contain the value prior to your change.
Free a Program from within a CL program. Useful for freeing RPG programs that were activated and are no longer needed. More granular than RCLRSC.
The FTP2 (Start TCP/IP File Transfer) command allows the use of FTP without entering the FTP subcommands. The subcommands are generated internally and used to send a file to a remote system. A log of FTP subcommands, errors, and information is kept to allow error reporting.
The Generate Prime Numbers command writes one record per prime number to the PRIMEP file. Each number is 7 digits in a packed field named PRIME. A range of prime numbers may be generated from 2 to 9,999,999. Prime numbers may be helpful in different applications. The algorithm used is a modified Sieve of Eratosthenes. The model outfile is TAANBREP with a format name of PRIMER.
Generate a Random Number. Useful for creating test data, simulations, games or achieving a relative record number.
The Generate Random Password command generates a random password of a specified length from 5 to 100 bytes. Options exist to allow digits, allow vowels (AEIOUY), and allow lower case. No adjacent characters will ever be the same. The first character is always an upper case letter A-Z that is not a vowel. The second character is always a digit if digits are allowed.
The Generate Random Password 2 command generates a random password according to the system password rules which are set. This tool is available only on IBM i 7.2 and later.
The Generate Unique Number tool generates unique numbers within a specified range. The GENUNQNBR command is intended for CL program use and generates a single unique number each time the command is used. The GENUNQNBR2 command creates an outfile of unique numbers. The outfile name is always UNQNBRP which uses the model file TAANBRDP with a format name of UNQNBRR.
The General Data Base File tool provides a simple ready to use data base with standard fields. The tool is intended for applications where a simple internal data base file is needed for the application and actions must occur from a CL Program. The tool is designed for low use activity.
The Grant Authority to Message Queue command is intended to prevent the *PUBLIC user from displaying and answering messages in a message queue such as QSYSOPR. The command sets the *PUBLIC authority to allow sending of messages, but prevents the use of DSPMSG to the message queue. A named user may be specified who will be able to both send messages and use DSPMSG.
Grant Owned Objects. Grants authority to a user for all of the objects owned by a different user. No QDOC documents are granted to. A companion command (RVKOWNOBJ) performs the revoke function. A spooled file lists all the changes.
The Grant User Group Authority command allows you to grant the same authority to all users of a User Group (as defined by the User Group tool). The companion command is RVKUSGAUT which revokes authorities to an object for users of a User Group. These commands can be helpful when groups of users are needed, but the system Group Profile support cannot be used or is undesirable to use.
The Hash Two Fields command provides for two fields to be input and returns a 10 byte hash value. The typical use of the function is when a non-secure program exists that needs to be passed data and you want to prevent the misuse of the program.
Help TAA Menu. HELPTAA is both a command and a menu (access via GO HELPTAA). The menu provides both information members about the TAA Productivity tools (e.g. Overview, Security, Libraries used, and typical commands to assist you in finding the right tool and understanding it (e.g. DSPTAACAT, PRTTAACAT, DSPTAACMD, WRKTAA, DSPTAA).
The Hold All Job Queues command holds all job queues in one or more libraries using generated HLDJOBQ system commands. A single job queue name, a generic name, or all job queues may be held. An ACTION parameter allows either *CHECK or *HOLD. HLDALLJOBQ can assist when a full or partial shutdown of the system is needed. You must have both *ALLOBJ and *JOBCTL special authority to use HLDALLJOBQ. See the companion tool RLSALLJOBQ.
The Hold All Output Queues command holds all output queues in one or more libraries using generated HLDOUTQ system commands. A single output queue name, a generic name, or all output queues may be held. An ACTION parameter allows either *CHECK or *HOLD. HLDALLOUTQ can assist when a full or partial shutdown of the system is needed. You must have both *ALLOBJ and *JOBCTL special authority to use HLDALLOUTQ. See the companion tool RLSALLOUTQ.
The Hold All Writers command holds all writers by using generated HLDWTR system commands. A single writer, a generic name, or all writers may be held. An ACTION parameter allows either *CHECK or *HOLD. HLDALLWTR can assist when a full or partial shutdown of the system is needed. You must have *JOBCTL special authority to use HLDALLWTR. See the companion tool RLSALLWTR.
The Hold Job Until command allows you to release a held job at a specific time. You can either use HLDJOB to hold the job or submit the job with HOLD specified. The job being held cannot be an interactive job. You can release the job either in the current day or the next day. HLDJOBUNTL may be helpful when you want to hold a job for a period of time and avoids having to remember to release the job.
The Hold Job 2 command holds one or more jobs using the system HLDJOB command. Generic job names or user names may be specified along with a subsystem name. An ACTION parameter allows either *CHECK or *HOLD. HLDJOB2 can assist when a set of jobs needs to be held. You must have *JOBCTL special authority to use HLDJOB2.
High Level Language Remove Message. Provides a program to call (HLRMVMSG which has no parameters) from a HLL to allow removal of all the messages received to the HLLs program message queue. Allows cleanup of the job log for HLL program message queues.
The Horse Race tool provides the ultimate method of choosing who should buy coffee. Up to 7 horses may run in each race. The race lasts less than a minute.
The IFS List tool provides commands to create a list of IFS Directories that may be used with the CVTIFS OBJ(*IFSLST) and CAPSYSINF IFS(*IFSLST) functions. This provides a specific set of directory names that will be converted. This allows you to minimize the time it takes to do CVTIFS or CAPSYSINF to the IFS directories you are interested in.
The Indent CLP Source command provides for a method of indenting CLP source DO groups within a source member. The DO command may appear by itself or be embedded in an IF, MONMSG, or ELSE command. This can simplify viewing CL source as the DO groups clearly standout.
The Initialize Password tool is designed for Assistant Security Officers to be able to reset a users password. The typical case for this would be where the user has forgotten his password. The INZPWD command allows the new password to be either the user profile name or a random value. The INZPWD2 and INZPWD3 commands force a random value. Either command forces the user to change the password at signon.
Job Log control. Provides a method of capturing job log information and placing it in data base files. A sub file display allows the job log data to be found by using one of several access paths. The job log data can be displayed online or printed with options to reduce the amount of printing.
The Job Accounting tool is a series of commands that let you work with the job accounting entries from the QACGJRN journal. You may either display the entries using several different access paths or print the entries using different selection and sequencing criteria. Job accounting entries from multiple systems may be stored in the same data base.
The Job Active tool provides a periodic check for critical jobs that are designed to be active at all times. If one of these jobs is not active, a message may be sent to QSYSMSG (QSYSOPR is used if QSYSMSG does not exist) or a command may be run.
The Job Analysis tool submits a never ending batch job to capture WRKACTJOB information at specified intervals. Options exist such as sending a message if a job has used more than a specified amount of CPU percentage during an interval. The JOBANZ tool can assist in determining which jobs and conditions are causing a slowdown in system performance.
The Job Dependent tool provides a series of commands that allow a Master Job to be defined with Dependent Jobs. Each Dependent Job can be defined to have dependencies such as the successful completion or failure of another Dependent Job, a switch setting, or if an object exists. At various points, the Dependent Jobs are tested to determine if their dependencies are met and if so, a Dependent Job is submitted to batch.
Describes a demonstration for the JOBDEP tool.
The Job Information tool provides commands that allow you to create a record when a job begins and ends. The information that is captured includes how and when the job started and a summary of performance information when the job ended. The STRJOBINF and ENDJOBINF commands must be included in the job.
Job Scheduling. Provides a method of storing SBMJOB commands in a file with a group name (e.g. MONDAY, TUESDAY, MONTHEND) and allows a simple method of submitting an entire group. Useful for simplifying system operator tasks for submitting standard batch work.
The Job Talk tool allows a means of interrupting a job to execute a command entered from another job. The job to be interrupted must set a message queue to Break Mode and use a supplied Break Handling program. The technique allows an authorized user to display the contents of objects that cannot ordinarily be seen such as *LDA, *GDA, and objects in QTEMP. The same technique may also be used to assist in recovery.
Lock First Record in a Data Base File. This is a testing aid which will lock the first record in a keyed or arrival sequence access path. A program in a second job can be tested for how it handles a locked record condition. Useful for testing.
Library groups. Allows a series of library groups where each group is one or more libraries. The CHGLIBGRP command allows the user portion of the library list to be set by naming a list of library groups. ADDLIBGRP and RMVLIBGRP are also supported. Useful for changing library lists without changing programs and for simple list switching when the maximum number of allowed libraries (25) is being approached.
Limit DLTSPLF. Provides a solution that prevents users without *JOBCTL special authority from deleting a spooled file by using a validity checking program. The commands DLTSPLF and CLROUTQ can be limited. The CHGSPLFA OUTQ parameter can also be limited. An option exists to limit to *SPLCTL special authority instead of *JOBCTL.
Limit DLTSPLF 2. The same as LMTDLTSPLF for DLTSPLF except that more granular control may be used to specify what can occur by spooled file name. For example, deleting a QPJOBLOG spooled file can be limited to *JOBCTL or *SPLCTL users or by an authorization list.
Language Message File. Helps provide a solution for systems that have users operating in multiple languages. The tool allows application access to a standard function to determine what message file to override to.
Locked Record Message. Describes a standard method of producing a separate display when a locked record condition occurs. Allows a program to send to the interactive user or to the system operator a message describing the locked record condition and who has the lock. Reply options include 1) Try again, 2) Send a message to the user who has the lock, or 3) Send a message to the system operator, and 4) Cancel (optional).
The Lock Wait tool provides commands to check for jobs in a LCKW status as seen with WRKACTJOB. RUNLCKWAIT provides job log messages if jobs are waiting for a lock. SBMLCKWAIT submits a never ending batch job that sends messages to a message queue if jobs are locked. The LCKW value can be caused by either a job waiting for a record lock or an object lock.
Log CL Statements. Provides a simple key stroke savings for invoking CHGJOB LOGCLPGM(*YES). Requesting logging allows a form of debugging of CL programs without going to debug mode.
The Lookup command provides a search within a CL program of a character variable that is an array of equal length elements. The variable must be declared as *CHAR LEN(32000). An alternate array may be specified and the corresponding element returned after a successful lookup. The alternate array variable must also be declared as *CHAR LEN(32000).
The Lookup 2 command provides a search within a CL program of a character variable of 32,000 bytes that is an array of equal length elements. An option allows the insertion into the first blank element. Another option allows a shorter length for the lookup argument to enable additional information to be stored in each element.
The Lookup 3 command provides a simple lookup capability to check whether an argument exists in an array. The array can be a large CL variable of up to 5,000 bytes. A generic search argument is supported.
The Love SEU command blanks out the text of the EDT0630 message of QEDTMSG in QPDA that is used to describe the ‘modern alternative to SEU’. If you love SEU, you can blank out the message and prevent having to see the words over and over again. The message ID changed is EDT0630.
The Mail Address tool is a series of commands that allow you to create and maintain a list of E-Mail addresses. The MAILADR tool is required to use the SNDxxxMAIL commands unless a specific E-Mail address is entered. MAILADR allows an optional logging of anything sent by the SNDxxxMAIL commands.
The Module Use tool allows you to capture information about the modules in ILE programs or service programs. A subfile display provides a ‘where used’ capability of what programs contain the same module. A second subfile display provides a simple review of modules by program. You must first convert the information from ILE *PGM and *SRVPGM objects.
The Monitor Message Queue tool provides a simple solution for monitoring a message queue for specific message IDs so that an action may be performed. For example, you may want to call a program when a specific message arrives on a message queue such as QSYSMSG. To use MONMSGQ, see the ‘Getting started’ instructions.
The Move All Objects command moves one or more objects from one library to another. An option allows a determination of what processing should occur if the object already exists in the To library. The default moves only objects that do not exist in the To library.
Move Character to Decimal. Rarely required, but allows a packed data value defined as character in CL to be moved (not converted) to a decimal field. Useful when packed data appears in a character field and must be changed to decimal.
The Move CLP DCLs command moves DCL and DCLF statements from anywhere in CL or CLLE source to the correct place in the source. This allows you to enter a DCL statement when you are coding and then use MOVCLPDCL before compiling the program.
The Move by Create Date command moves objects from one library to another based on a range of object creation dates specified. Because ACTION(*CHECK) is the default, no objects are moved and a listing describes those that would be moved. If ACTION(*MOVE) is specified, the objects are moved.
The Move Decimal to Character command moves a *DEC value (packed data) to a *CHAR LEN(8) variable and retains the packed representation. The data is right adjusted in the return variable. This allows the data to be passed to other functions which require a packed representation.
The Move Job command moves one, generic, or all jobs from one job queue to another. Selection may be made on a specific or generic job or user name. MOVJOB simplifies moving jobs.
Move Library Objects. Move some or all objects in a library to a different library. Options for specific object type, generic names or all objects beginning with other than Q. Useful for mass moves.
Move Member. Move a member from one file to another. Helpful for handling source when members must be moved from one source file to another. It uses CPYSRCF and then removes the member from the FROMFILE.
Move Many Objects. Allows a list of objects of differing types to be moved. Each object is moved using MOVOBJ. Useful for mass moving of objects.
The Move Message Description command moves one, a range, or all message descriptions from one message file to another. Any message IDs that are moved are removed from the From message file. A listing is displayed or output of all messages moved and any errors that have occurred.
The Move Old Objects command moves objects to a specific library that have not been used since a specified date. A list of libraries (including generic) may be specified. This allows for cleanup functions to occur.
Move Spooled File. Moves one or all spooled files from one output queue to another. Options are provided to move only those spooled files meeting a certain status (e.g. RDY) a specific USER or specific USRDTA. Useful for automating the movement of spooled files from one queue to another.
The Move Spooled File Output Queue command is a special purpose function intended for the case when CVTOUTQ cannot be used because the number of spooled files exceeds the 16MB limit of a user space (approximately 160,000 spooled files). MOVSPLOUTQ reads the WRKOUTQ spooled file and moves a specified number of spooled files.
Move To Decimal. Performs an RPG MOVE like operation where no decimal alignment is performed. Useful for avoiding the rules of CHGVAR which forces decimal alignment. The companion command MOVTOCHR allows a move from a decimal field which has decimal positions to a character field without the result containing a decimal point.
The Merge Directory Entry tool allows the user to merge a single or all directory entries using a user generated file as input. The file would typically be created by the CVTDIRE command which is part of the same tool. The intent of the tool is to allow you to copy directory entries from one system to another.
The Merge Objects command is intended for the case where you batch the changes that are to go into production. The command handles the merging in of normal objects, data base networks, and source members. Either new or replacement objects/members are handled. An option exists to retain or replace the production data. The command can be used on the same system or a remote system.
The Merge Spooled Files command combines all spooled files from an output queue into a single spooled file. This essentially makes a book out of multiple chapters. You are responsible for using the same spooled file attributes (such as LPI) for all spooled files being combined. Only standard DP output is provided for (no special graphics).
The Merge User Profile command allows for the case where you want to transfer ownership, authorizations, etc of one user to another user profile. Owned objects, authorizations, spooled files, names within Job Descriptions, and names within Job Schedule entries are changed. If successful, the From user profile is deleted. The name within user data or TAA objects is not changed.
Message Control. Allows automation of a message queue. Provides a method of programming a message queue (e.g. QSYSOPR). Aimed at environments that want to 1) Run unattended, 2) Run mostly unattended, or 3) Reduce the number of messages that an operator must deal with in QSYSOPR (show only important messages). Uses a data base file to describe the actions. Allows forwarding of specific messages including the proper handling of inquiry types.
The Maintain All Journals command provides a simple means of creating and deleting journal receivers for all journals on the system. The command is intended to be run just prior to a backup. This allows for a full save of the recently detached journal receivers and deletes any old journal receivers that are already saved. A listing is provided of all journals and journal receivers with any action taken.
Maintain Journal. Provides a simple solution for changing journal receivers. Allows a special value for the system supplied journals to be handled.
The Maintain Journal 2 command provides the ability to delete old receivers (and add a new receiver) to one or more journals. Both system and user journals may be specified.
The MY Q tool is a series of commands that lets you send and receive entries to a simple queue. This allows one program to place the entries on the queue and a second (or the same) program to receive them in a loop or by an entry number. The queue is a *USRSPC object that can contain up to 8,000 entries. All commands default the name of the queue to MYQ in QTEMP. A specific queue and library may be named.
The Name and Address tool is designed to allow you to key in names and addresses (such as from business cards) and then find a name by using a simple search technique. Each user can have his own unique data base or a data base can be shared by multiple users.
The Number Counter tool provides the best performing solution for the case where a consecutive number must be assigned for multiple jobs. For example, the NBRCTR tool should be considered if multiple operators are entering orders and each order should be assigned the next consecutive number.
The No Op command does not perform any operation. Its function is to allow a command to be specified when one is required for a specification, but no run time function is needed. A completion message is sent if the command is run.
Note file. A program that allows you to add notes (text comments) to an application. Each unique key can have an optional master note and up to 9 notes per day. Each note is a display of 14 lines with 75 bytes per line. A demonstration command exists to assist you in understanding the tool.
The Object Type tool provides four source members for use with the CPYCMD tool. Only source is provided. The source is intended for command definition involving a typical object type parameter. No command object or program exists.
The Open Spooled File command is a testing aid. It allows a spooled file to be opened with a specific name and remain open. The intent of OPNSPLF is to allow other functions to test how they operate on an opened spooled file.
Logical OR. Or’s two fields together. Useful for scrambling data. Used by the SCRAMBLE function.
The Outfile Fields tool is a series of commands that allow you to display a field name that exists in either a system and/or TAA model file. This can assist in understanding the attributes of the field and the command which outputs the file. After the required files are created and the field information is converted, the DSPOUTFFLD command can be used.
The Page Separator program allows you to have large block letters for spooled job or file page separators. Up to 3 values of 10 characters each may be written as large block letters. Each block letter is 10 x 10 in space with the character taking up 8 x 10. Options exist to tailor the values that print as block letters such as job, user name, originating system, user data, etc.
The Parse command allows the parsing of an input value into one or more return variables. A list of separator characters must be specified (default is ‘blank’) to determine how the input value should be parsed. Up to 30 return variables of a maximum length of 200 bytes may be returned. PARSE is not intended to parse an i5/OS command string.
The Pause command displays an entire screen with each line containing text as supplied on the command. By default, the display ends when the operator presses Enter. An option exists to end the display after a number of seconds or when the operator presses Enter. This approximates a full screen status message, but does not allow the program to continue until the function ends. PAUSE can be helpful in describing conditions to a user.
The Program Adopt tool provides a series of commands to help manage the programs that adopt a user profile during the running of the program. This allows a review and approval of these programs and a method of monitoring for changes.
Package Source. Provides a solution for re-making user changes to source shipped from a vendor when a new version of the source is supplied. Requires special comments be placed in the source. The re-making of changes should be automated in most instances. Supports the MRGPKGSRC and CVTPKGSRC commands.
The Prompt Command command is intended for situations where a command is entered into a field that will be checked by QCMDCHK. If the command to be entered should be prompted, QCMDCHK ensures that all required parameters are entered. PMTCMD allows you to enter just the command name. You may optionally enter some keywords and values and determine if a keyword value should be protected.
The Prompt Field command is intended to be used in an application where the user should select a few fields from an externally described data base file. A subfile is displayed of the fields in the record and the user can select the fields to be returned. The fields are passed back in a return variable.
Prompt Operator. Prompts an interactive operator for a single value and provides error checking against the value. Useful for eliminating CL validity coding when the operator must be prompted to supply a single value.
The Prompt Operator 2 command is a simpler version of PMTOPR and DSPWINDOW. It allows a CL program to display a window and optionally allow an F12 for Cancel and/or a Y/N return value. Up to 6 lines of text may appear plus a title. PMTOPR2 provides a simple method of communicating with an operator.
Print from a CL Program. Allows a CL program to perform printing by use of a command. Useful for eliminating simple print programs when the data is already available in a CL program. See also BLDPRTLIN.
The Protect Library tool helps prevent specified critical libraries from an accidental use of CLRLIB or DLTLIB. The tool uses the system provided command exit program technique. In addition to CLRLIB and DLTLIB, the TAA Tools CLRLIB2 and DLTLIB2 are also protected. Not even an *ALLOBJ user will be able to accidentally clear or delete a protected library.
The Print Accounting tool is a series of commands that let you work with the print accounting entries from the QACGJRN journal. You may either display the entries using several different access paths or print the entries using different selection and sequencing criteria. Print accounting entries from multiple systems may be stored in the same data base.
Print Adopted Program. Provides better output than the system command DSPPGMADP. The users special authorities are printed and more information about the program is shown. The command should assist you in identifying the programs that adopt the users profile so they may be examined further by the TAA Tool PRTPGMSEC.
Print Adopted Programs 2. Provides an analysis of the programs in a library that adopt the owners profile. Performs checking of the program and sub programs to assist in determining if the programs are written so they may not be exploited for non-secure functions. Differs from the PRTADPPGM tool in that the format is intended more for periodic reviews of an existing application rather than system wide checking.
The Print All Job Queues command prints one line per job queue for one or many job queues. Each line has the total number of jobs by RLS, HLD, and SCD categories and the subsystem the job queue is attached to (if any). Options exist to bypass job queues that do not have any jobs and select those which have jobs that match a status such as HLD.
The Print All Output Queues command prints one line per output queue for one or many output queues. Each line has the total number of spooled files, the number of pages to be printed, and the allocated size of the spooled files. Options exist to bypass output queues that do not have any spooled files and select those output queues that have spooled files that match a status such as HLD.
The Print All Source Files command prints a list of all source files in one or more libraries. Each line of information includes the owner, number of members, last use date, the last change date, and member description.
The Print Area Codes command prints a listing of the area codes for the major cities in the USA and Canada. An option exists to print all the area codes in a state or province. The RPG provided program may also be used to retrieve the array data used.
Prints ASP Libraries. Prints the libraries in one or all ASPs. Useful for determining what libraries exist in a user ASP.
The Print ASP Overflow command prints the objects that have overflowed in a specified ASP (Auxiliary Storage Pool). Both the new and old style ASPs are supported. You must know the ASP that has overflowed. This can be determined by using STRSST.
Print ASP Use. Prints a summary with one line per ASP, describing the amount of storage and the percent used. The information from WRKDSKSTS is used and summarized. Useful for managing user ASPs.
Print authorization list. Provides a method of a simple security review of who is authorized to one, generic, or *ALL authorization lists. Useful for Security Officer review.
The Print Authorization List Objects command prints a listing of one or more authorization lists and the objects that are authorized to each list. The system command DSPAUTLOBJ, lists only a single authorization list. See the PRTAUTL command for the user authorizations to the lists.
Print back to back. Provides a solution for printing a spooled file back to back by allowing creating two spooled files for the odd and even numbered pages. After printing the even numbered pages, the paper should be reloaded to print the odd numbered pages. The command PRTBCKBCK prints a single spooled file. PRTBCKBCK2 prints all spooled files in an output queue.
Print Big Character. Prints 12 x 12 characters. Converts up to a 10 byte value and returns a data structure of 12 lines of 140 bytes each (total of 1680). The CPP can be called directly. Useful for printing large headings.
The Print Big Object tool assists in determining the large size objects on your system. This can help cleanup of a system. One or more libraries may be processed by a single command. An optional exception file may be used to avoid flagging those objects which are known to be large.
The Print Blank Object Text command prints one line per object in a library or libraries where a blank text description exists. This provides a convenient review of where programmers are not including a text description.
The Print Blank Source Text command prints a listing of source members that have a blank member description. All source files are checked in one or more libraries. The command is useful for cleaning up source files to ensure that a text description exists.
Print Changed IBM Objects. Print the objects in system libraries that have been modified by user commands. For example, it finds the commands and printer files in QSYS that have been modified. Useful before install to determine what needs to be done after installing a new release and also for reviewing system changes.
Print Changed Message Descriptions. Provides a listing of all changed message descriptions in a message file. Useful before install to determine what needs to be done after installing a new release and also for reviewing system changes.
The Print Change Summary command prints one line per source member and describes the number of changes that have occurred from a specified date. This provides a good review of what has changed in a source file. By default, only the changed members are listed.
Print CLP DO Groups. Provides an indented listing of CL source that shows the DO Groups. Useful for understanding the logic of a CL program or finding the error when an unbalanced DO group error is noted by CRTCLPGM. See also DSPCLPDO.
Print Command Use. Prints the usage information about commands in one or more libraries. Useful for understanding how a system is being used.
The Print CPYSPL2 command provides an inverse function of the CPYSPLF2 TAA function. CPYSPLF2 creates a data base file from a spooled input file with blank lines and a new page indication. This allows a display of the data using a program rather than DSPSPLF. PRTCPYSPL2 reads the outfile created by CPYSPLF2 and re-generates a spooled file.
Print Create Date. Prints object or member level information and allows you to sequence on create date. Assists in understanding how your system was put together.
The Print by Create User command prints the objects in one or more libraries by the user who created the object. This may not be the current owner of the object. The user who created the object may not exist on your system. Selection can be used on a minimum create date, a minimum last used date, and the size of the object. PRTCRTUSR can be helpful in cleaning up the system if group profiles own most of the objects.
The Print Conversion Required command prints the programs on a RISC system that are not usable because conversion from CISC to RISC is required. The listing also includes information on whether the source exists on the system.
The Print Data Base file command allows you to print specific fields from a file without creating a program or query. The field name is used as the column heading with an option for the DDS column headings. Any decimal fields are added, averaged, and the maximum and minimum values are shown. PRTDB is useful for programmers or simple reports.
Print Data Base File Analysis. Provides for an analysis of how physical data files are growing. ADDDBFANL is used periodically to capture the member information. PRTDBFANL is used to compare the information from two different dates. RMVDBFANL provides for cleanup of the saved information. Useful for determining growth.
The Print Data Base File Exceptions command prints a listing of files and members where the current status exceeds either a specified percentage of deleted records, a size of deleted record space (number of deleted records times record length), or the number of records exceeds a percentage of record capacity.
The Print Data Base File Size command prints a listing of the physical members of a file and any dependent logical files. The sizes of each are shown and totaled. A single file, generic files, or all files in a library may be processed. This provides a simple means of determining the amount of space being used by specific files and their dependent access paths.
Print Device Configuration to a Source Member. Allows the capturing of the details of device configuration without printing paper. Provides backup information if the device configuration is subsequently changed incorrectly. Access of the data can be made using the SEU scan function. Can use just prior to major backup points to save the configuration.
Print Deleted Record Numbers. This command will print any deleted record numbers found in a data base file. Useful for understanding where the deleted records are and the makeup of the file.
The Print Data Area command is a simple front end to the DSPDTAARA command that provides only printing output (no display). The intent of the command is to make it easier to force a print only function such as is needed by the JOBTALK tool.
Print Generic Source. Prints all of the source for a generic name from a single file, all standard source files (e.g. QCMDSRC, QCLSRC), or the QATTxxx files. The TAA tool PRTSRCF is used for printing. Useful for a simple means of printing related source.
The Print Group Profile command prints one or all group profiles along with the members of each group. The listing contains more information than the system commands which display group profiles. PRTGRPPRF provides for a better review of your group profiles and the members of the group.
The Print IFS command prints one line per directory type of object in the IFS plus summary information about the objects within the directory. Summarizations by owner and type are also provided. The outfile from the TAA command CVTIFS is used for the data. This provides a simple review at the Directory level.
The Print Job Queue Authority command prints a listing of all job queues in one or more libraries. The important security options such as OPRCTL and individual authorizations are listed for each job queue.
The Print Job command is a front end to the system DSPJOB command to print the information. The command is intended to be used with the JOBTALK tool or anytime a simple listing of the job information is needed.
Print Job Accounting 2. This is the old form of PRTJOBACG. Prints some basic reports from the job accounting journal. Different sequencing options are available along with totals by CPU, transactions, auxiliary I/O etc. Useful for basic job accounting information as well as simple performance analysis.
The Print Job Queue Time tool provides assistance in answering the question ‘How much time is spent by batch jobs on a job queue waiting to go active?’ You must be using the TAA Job Accounting tool. The CVTJOBQTIM command is used first to select records from the JOBACGP file and create the JOBQTIMP outfile. The PRTJOBQTIM command may then be used to print a listing with various selection and sort criteria.
The Print Job Summary command allows an analysis of the QHST CPF1164 messages. Records may be selected by date, job, user, job type, and completion code. The amount of CPU time, transactions, and average response time are listed for each job.
Print Journal Analysis. Analyzes the journal entries and prints a summary by file/member of the activity (i.e. the number of opens, closes, adds, updates and deletes). Options exist for a more detail summary by user or program. A summary of the other journal entries found is provided.
The Print Journal Analysis IFS command analyzes the IFS Journal Code entries (JOCODE = B). You must first create an OUTFILE using DSPJRN with a *TYPE1 format. Only the B entries are selected and sorted. You may cause a control break on the object, program within object, or user within program within object.
The Print Journal Code command prints the system defined journal codes and their descriptions. This includes the sub code used by the ‘T’ audit entries.
The Print Journal Receivers command prints a listing of journal receivers and allows a minimum size. The size of each is shown along with the attach and detach date. This provides a simple means of reviewing large journal receivers.
Print Journal Summary. Finds the journals in one or more libraries and prints a summary of the receivers and the number of physical files and access paths being journaled. Useful for determining the existing journals and a summary of the activity.
Print Library Analysis. Analyzes one or all libraries for summary totals of object types and a breakdown of file and program types. Provides a variety of feedback such as whether the save strategy is current, ASP summary, owner summary, and source summary. Useful for a periodic checkpoint for what your system looks like.
The Print Library Authorizations command prints the object authority information of objects within a library and the library object. This can be helpful in reviewing security. See the PRTLIBAUT2 tool for printing authorities to library objects (not the objects within a library).
The Print Library Authority 2 command prints the authorities of users to library objects (not the objects within a library). Different options exist for the list of libraries, the type of libraries, library ownership, and if only a single user’s authorities should be printed.
The Print Library Count command prints a one line summary per library or multiple libraries. The tool differs from PRTLIBANL in that an API is used to access the object information (performance of PRTLIBCNT is better), but member and record information is not provided.
Print Library Detail. Prints all object types, a selected object type, a selected object attribute (e.g PF) or a selected owner in a library. Performs the same function as DSPLIB with a different output format and selection criteria. Output includes the use and change date information, the owner and the last source change date.
Print limited commands. Prints a listing of the commands that are specified as ALWLMTUSR(*YES) in a library or libraries. Both system and user written commands can be analyzed. Useful for determining the commands that can be used by users who are LMTCPB(*YES).
Print Last Change Date Information. Objects or members are printed based on the last change date. Options exist to define a cutoff date and to sequence on the date. Useful for assisting in understanding how the system is changing.
Print Last Use Information. Objects or members are printed based on the last use date. Options exist to define a cutoff date and to sequence on the date. Useful for assisting in cleaning up the system.
The Print Last Library Use 2 command is designed to assist in cleaning out unused libraries. A listing is produced with one line per library and the date of the most recently used object within each library. The user must be authorized to the TAADSPADP authorization list.
The Print Level Check command provides a comparison of the formats stored within a program with the files to be accessed at open time. This can help pre-determine any level check problems. A single program, generic programs, or all programs in a library may be checked. A spooled file is output.
The Print Member Summary command prints a listing of all data base files in a library with one line per file. The number of members and the save date of the files are shown. Totals by PF-Dta, LF-Dta, and PF-Src are provided. PRTMBRSUM may be helpful to review how many members exist in a library.
Print Many Source File Members. Prints many source files members using the TAA tool PRTSRCF. Useful for documentation.
The Print Non-IBM Objects command is designed for use when converting from one hardware system to another. If any user objects have been accidentally placed in system libraries, they will be lost if only user libraries are restored. PRTNONIBM can help find any user objects that may exist in system libraries.
Print Non-Observable Programs. Prints the programs in a library or all libraries that have had observability (debug information) removed. An indication of whether the source still exists in the originating file/member is also made. Useful for determining the programs that could cause problems if the system requires a retranslation.
The Print Non-TAA Objects command prints a listing of all of the Non-TAA objects in TAATOOL. The ‘date of last use’ and the ‘days use count’ information is also provided. This can be helpful in determining what non-TAA objects exist that may be used in user source such as the HLRMVMSG program. See also the “Determining TAA Tool usage” option on HELPTAA.
The Print Output Queue Authority command prints a listing of all output queues in one or more libraries. The important security options such as DSPDTA, OPRCTL, and individual authorizations are listed for each output queue.
The Print Outfiles command prints a listing of most system commands that support the OUTFILE parameter and all TAA CVT commands that perform an outfile function. The model file and format are shown for each file. The processing program may also be called to receive the same information in an array.
The Print Owned Objects command prints a listing of owned objects. The command is similar to the system DSPUSRPRF TYPE(*OBJOWN) function, but provides better output (such as last change date, last used date, size, etc). You can select on the last used date and a minimum size to reduce the number of objects that will be listed.
The Print Page Of command allows you to re-print a spooled file where you have printed ‘Page n’ and change the value to ‘Page n of n’. You must identify where the units position of the page number is and the line it is to print on. After re-printing, the original spooled file is deleted.
The Print Page Range command offers a convenient method of printing a subset of a spooled file. PRTPAGRNG does CPYSPLF and then prints a spooled file that will contain only the requested pages. Only normal DP output is supported (no special graphics). PRTPAGRNG may be used in some cases when the system spool support cannot be used or has restrictions when using a page range.
Print Program Attributes. Prints the common attributes of a program, generic programs or all programs in a library. Selection criteria exists such as printing only those with LOGCLPGM(*NO). Useful for finding exceptions or ensuring consistency for programs in a library.
The Print Program Calls command prints a listing of the calls from a program and optionally cascades to print the calls used by any sub programs. Parameter lists may optionally be printed. Only CL and RPG along with single module CLLE and RPGLE programs are supported.
Print Program Security. Intended to assist you in understanding the security implications of a program. The information is available from the system, but it takes several commands. PRTPGMSEC brings all of the information together and highlights the functions to be reviewed. Tips for obtaining better security are provided. Useful for security reviews.
Print Program Stack. Provides a testing aid. It prints the current program stack and provides as much information as possible relative to the security considerations of program adopt and the CHGPGM USEADPAUT(*NO) function. It also allows you to specify an object and see the user’s authorization to the object. Useful as a testing aid in determining the program stack picture at a specific point and authorization considerations.
The Print Phone International command prints a listing of the prefix phone codes used for international long distance. You may search by prefix or country abbreviation (such as POR). An option exists to print all countries by prefix. Only major cities are supported and many cities in English speaking countries.
The Print Profile User command lists profiles with *ALLOBJ authority, along with profiles that have *USR authority or greater to those profiles. The report is generated into a spool file, PRTPRFUSR. This gives some insight as what profiles can gain *ALLOBJ authority.
Print Parameters. A series of commands that print the parameters of a specific object, generic objects of the same type, all of the types in a library etc. Each object is printed on one line followed by a line for each of the parameters where the default is not used. All the commands begin with PRTPRM and then the specific type (e.g. PRTPRMPF). Useful for reviewing what has been specified that differs from the defaults.
The Print PTF Summary command prints a summary of the PTFs by status within Product ID. This provides a review of the PTFs with a count and summary by status. The user must be authorized to the DSPPTF command. The command may also be helpful prior to installing a PTF Cumulative Package to determine if any ‘Not applied’ conditions exist.
Print QHST Analysis. Analyzes the information found in QHST. The major analysis is based on the CPF1164 job completion message. These are summarized by day, by completion type, and by user. Other significant messages are listed and counted. A general count is provided for each unique message ID. This can be used for a basic form of job accounting.
The Print QTEMP command prints a listing of the objects in the current jobs QTEMP library. The command is intended to be used with the JOBTALK tool or anytime a simple listing of the current jobs QTEMP library is needed.
The Print Reverse command prints a spooled file in reverse page order by creating a new spooled file. For example, if 3 pages exist, the new spooled file would contain page 3 as the first page, page 2 as the second page, and page 1 as the 3rd page. The lines per page are printed in the same order as they appear in the original spooled file.
Print RPG DO groups command prints RPG source and provides an indentation of the DO groups (including IF, CAS, and SELEC groups). Both RPG III and RPG IV formats are supported. PRTRPGDO is useful for program documentation and can be of assistance when attempting to understand the flow of a program.
The Print Save Audit command is intended to provide a listing for an auditor after a significant save has occurred such as some combination of SAVSECDTA, SAVCFG, SAVLIB, and SAV. The critical messages from the job log are printed to a listing. An option exists to print the QSYS data area information instead and one line per library with save date/time.
The Print Save Count command prints one line per specified library with a size of the library, a count of the objects, and an estimate of the internal count of objects in the library. The command is intended for estimating save/restore requirements.
The Print Save Tape Labels command is intended to be run following a save operation and creates spooled output to be used as external labels for tape volumes. A save requiring multiple volumes is supported.
Print Save Status. Prints libraries and what media was used for a save. Useful for assisting in recovery in case it is necessary to know which libraries were saved or what media they were saved on.
Print Security Audit. Print a report for an auditor or Security Officer to review. The output includes such things as profile names that are eligible to signon, but have not done so in the last N days, profiles that use the profile name as the password, a summary of all the system and user profiles, storage owned by QDFTOWN, last save/restore information for user profiles, etc.
Print Security Violations. Prints security violations found in QHST. This command exists for compatibility purposes (the majority of violations are now placed in the audit journal). To use PRTSECVIL, the QHST file must first be converted with the TAA tool CVTQHST.
Print SEU Text. Provides a ‘low cost’ editor by allowing formatting statements to be keyed in with SEU to a text member. The PRTSEUTXT command prints the source into a formatted output. Provides a wide variety of text functions, but not everything. Requires the user to know SEU. Useful for creating letters and DP documentation when a text editor does not exist.
The Print Spool Analysis command analyzes a QSPL library. A summary by day or month may be made. The listing includes the number of members (empty or with data) and the corresponding sizes. PRTSPLANZ provides a summary of how much spooled data exists.
Print Source Changes. The statements that have changed between a range of dates are printed. A 132 position print line is used. A single member, generic members, or all members in a file may be printed. A summary with one line per member is an option. Useful for determining what changed in a range of dates.
Print Source File Member. Prints the source statements by default in a in 8 1/2 wide form. The sequence numbers and 72 bytes of the statement are printed. The date of change is only printed if an option is taken. A change bar date (denotes all records changed after a parameter date) is optional. Useful for documentation.
Print Source Summary. Prints a line per source member similar to DSPFD *MBRLIST. Options are provided to indicate the changed members based on a specified date and to only print the changed members. Another option allows use of the date of last change on the source statements rather than in the member header. Special values may be entered for the source file name (*STD and *QATT) to print the members from multiple files.
The Print Source Type command prints the standard source types as defined by SEU and the corresponding source file that is used. A supplied program may be called to pass back three arrays of the information (source type, source file, and description). Some defined source types have no corresponding file and *NONE is returned.
Print System Analysis. This combines the TAA tools of PRTSYSSUM, PRTQHSTANL, and PRTLIBANL into a single command.
Prints System Summary. Prints a summary of the important system information such as size, last PTF package applied, critical system values, storage used, and critical save dates.
Print TAA Categories. Provides a listing of the tools by category with one line per tool. All or individual categories may be listed. An option exists to print the summary description for each tool listed.
The Print TAA Categories 2 command prints a listing with one line for each of the TAA Categories. The primary purpose of the command is to provide a call interface to other programs which need access to the TAA Category array of values and descriptions.
The Print TAA Categories 3 command prints a single page with all of the TAA categories in multiple columns. The intent is to allow the page to be posted for quick reference when working with the DSPTAACAT and PRTTAACAT commands.
The Print Time Zone command prints a listing of major cities in the world and the time zone offset from Greenwich Mean Time (GMT). The RPG program may also be called directly to pass back the array of information.
Print Use Count. A report is printed by object or member based on the ‘days use count’ kept by the system. Options exist to omit those greater or less than a specified count and to sequence on the count. Useful for cleaning up the system or understanding those objects/members that are being used frequently or infrequently.
The Print User Space command prints the value of a user space in character and hex. 32 bytes of data are printed per line. A start and end position parameter are supported.
The Print User Storage command prints the storage used information by different sequences. Ascending or descending amounts may be specified along with a ‘group by’ parameter that allows the report by job accounting code, group profile, or user class. PRTUSRSTG allows an easy means of determining who owns the majority of user storage on the system.
Print i5/OS Calendar. Prints a page for each month of a specific year on an 8 1/2 by 11 page. This provides a ‘month at a glance’ approach and is intended for personal hard copy calendars. There is no connection between this tool and the Office calendar support. Useful for providing tailored personal calendars.
Query File. Provides a simpler version of the OPNQRYF command. Uses a ‘fill in the blanks’ solution to the QRYSLT parameter. Can be used for simple select/sort functions or to provide a ‘leg up’ on generating a full OPNQRYF command. The BLDQRYSLT command is useful in CL programs to allow a simpler approach to the QRYSLT parameter in the same manner. BLDQRYSLT returns a variable which is then specified as the QRYSLT value for OPNQRYF.
The Query Use tool provides commands to capture and display the files used in a Query. Both Query/400 (*QRYDFN) and Query Management (*QMQRY) objects types are supported. QRYUSE can be helpful when the files used by a Query have changed and the Query must be re-created.
Rebuild Data Base. Rebuilds data base structure and all of the dependencies (e.g. logical files and programs). Useful when a data base file has changed in definition (e.g. a field is added or increased in size). RBLDBF will find all of the dependent logical files and all of the programs that use either the changed physical or dependent logical files. The objects are re-created in a separate library.
The Reclaim Storage in Batch command is designed to allow you to run RCLSTG (requires the restricted state) in batch. This allows scheduling of RCLSTG using the Job Scheduler or the SBMJOB SCDDATE/SCDTIME function. The RCLSTG2 command which is a front end to RCLSTG is used as it provides a better historical view of the Reclaim Storage results.
The Reclaim Storage 2 tool is a front end to RCLSTG. It provides better documentation of the results of RCLSTG and keeps the history where it may be conveniently displayed. There is no reasonable means of estimating how long RCLSTG will take on a system other than your own experience.
The Reclaim System Profiles command is a damage recovery tool that resets the system profiles that are not intended to be signed onto (such as QDBSHR) to their original critical attributes. The API QSYRESPA is used.
The Receive Last Message tool supports three commands that can be used to receive the last message sent to the current programs message queue. The command interface may be used, but the major intent of the tool is to allow simple access to the last message received by a HLL program.
The Receive Message Key command receives a message from the job log (intended for a low level message). You must first run the RTVMSGKEY command (part of the RMVMSGKEY tool) to set a mark in the job log prior to running the function that produces low level messages. Then RCVMSGKEY may be used to receive either a specific message ID or a loop may be written to receive more than one message.
The Right Adjust Variable command takes a value such as ‘23@@@@@’ and adjusts it to ‘@@@@23’. RGTADJVAR is intended for character variables that contain decimal values. Both character and decimal return variables are supported. A value such as ‘-23,112.38@@@’ is also valid. Options exist to determine if special characters are valid.
The Reorganize All PFM (Physical File Members) command reorganizes all members in a physical data file if specified criteria are met. The system RGZPFM command allows only a single member to be named.
The Reorganize Library command reorganizes one, generic, or all physical files in a library or all user libraries. Source files are excluded. Options on the command allow for selection on the basis of deleted record percentage or space. A data base file may be used to specify other options such as 1) omit a file or library, 2) always reorganize, 3) use a different percentage or space requirement.
The Release All Job Queues command releases all job queues in one or more libraries using generated RLSJOBQ system commands. A single job queue name, a generic name, or all job queues may be released. An ACTION parameter allows either *CHECK or *RELEASE. RLSALLJOBQ can assist when bringing up the system after a full or partial shutdown. See the companion tool HLDALLJOBQ.
The Release All Output Queues command releases all output queues in one or more libraries using generated RLSOUTQ system commands. A single output queue name, a generic name, or all output queues may be released. An ACTION parameter allows either *CHECK or *RELEASE. RLSALLOUTQ can assist when bringing the system up after a full or partial shutdown. See the companion tool HLDALLOUTQ.
The Release All Writers command releases all writers using generated RLSWTR system commands. A single writer, a generic name, or all writers may be released. An ACTION parameter allows either *CHECK or *RELEASE. RLSALLWTR can assist when bringing the system up after a full or partial shutdown. You must have *JOBCTL special authority to use RLSALLWTR. See the companion tool HLDALLWTR.
The Release Job 2 command releases one or more jobs that are in a HLD status by using the system RLSJOB command. Generic job names or user names may be specified along with a subsystem name. An ACTION parameter allows either *CHECK or *RELEASE. RLSJOB2 can assist when a set of jobs needs to be released. You must have *JOBCTL special authority to use RLSJOB2.
The Remove All Logical File Members command is designed for the situation where a batch program will add many records to a physical file and one or more keyed logical files exist over the physical. Performance can be improved by using the two commands around the batch program. RMVALLLFM finds the dependent logical files and removes all of the members. ADDALLLFM adds all of the members back.
Remove All Messages is intended for programmers or system operators who generate a lot of messages in their interactive jobs and want to periodically clean house of all messages. The command has no parameters and can only be used interactively or in an interactive CL program. A confirmation prompt will appear.
Remove authorization list objects. Removes the authorization of objects to authorization lists. DLTAUTL cannot be used if objects are controlled by an authorization list. The command can be used as a testing aid if you have programs that build your security structure.
The RMVCHAR command is similar to the RPG IV %TRIMx functions. Unlike %TRIMx, RMVCHAR allows you to remove specified characters anywhere in a string of up to 1000 bytes. The length of the returned value may also be returned.
The Remove Empty Members command removes empty members in a data or source file. An ACTION parameter exists that defaults to *CHECK meaning a listing is produced of what would be removed if *REMOVE had been specified.
The Remove Ending Period command removes an ending period (‘.’) from an input text value if it exists and returns a variable without the ending period. This can be useful when resending escape messages that may have an ending period.
The Remove Equal Source command removes members from a test type of source file that are a 100% match to a corresponding member in a production type of source file. The default is ACTION(*CHECK) to allow you to see what would be removed by ACTION(*REMOVE). RMVEQLSRC can purge the members that are no longer needed in a test type of source file.
The Remove Generic Source command removes generic source members from a single file, standard source files, or QATTxxx source files in a library. The command can help simplify cleanup activities.
The Remove Last Character command sets the last character in a variable to blank. It is primarily intended for use when receiving escape messages that already have a period at the end of the message text and should be resent using SNDESCMSG (which causes a period to be added at the end of the text). The message text must be declared as *CHAR LEN(512).
The Remove Last Message tool provides a command, but the intended use is to call the function from a HLL program by using the program RMVLST. It will remove the last message sent to the HLLs program message queue. Useful for cleaning up low level messages that can cause a lot of clutter.
The Remove Message Description 2 command removes a range of message IDs or all messages from a message file. The default provides a listing of the message IDs that would be removed if ACTION(*REMOVE) was specified.
The Remove Message Key tool provides two commands (RTVMSGKEY and RMVMSGKEY) which should be bracketed around commands that produce messages (including low level messages) that need to be cleaned up. When developing CL programs, it is desirable to cleanup messages produced by functions within the program. Many system commands send messages to low level programs that cannot be removed by RMVMSG CLEAR(*ALL).
The Remove Message Queue Messages command removes selected messages from a message queue. The intent is to provide a ‘cleanup facility’ for message queues such as QSYSOPR. Different selection criteria can be used.
Remove Message Queue Messages 2 command allows a removal from one, generic, or all message queues for messages that are past a retention date. The default is to bypass any message queues with a name beginning with Q in a library beginning with Q. Other message queues may be specifically bypassed.
Remove member 2. Provides a method of removing members when the member may or may not exist. An option on the command allows a completion message if the member does not exist. Useful for when a CL program must ensure that a list of members must not exist.
The Remove Old Member command removes members that have passed a retention date. The date to check can be any or all of the create date, last change date, or last use date. The command may be used to clean up files where members are created for different periods. Only multi-member data files are valid.
The Remove Old Member 2 command allows you to retain a specific number of members in a file. The excess oldest members (based on member creation date) are removed. This can be useful when dealing with date oriented members. Only multi-member data files are valid.
Remove Old Messages from workstation message queues. Allows cleanup of messages which were sent prior to a specified number of days. Certain system message queues are implicitly bypassed and specified user message queues can also be bypassed.
The Remove QSYSMSG Messages tool allows both removal and archiving of messages from the QSYSMSG system message queue. Removal is done based on the number of days to retain the messages. Archiving is optional and provides for the QSYSMSGP file in QGPL. If archiving is used, all new messages (not previously archived) are copied to QSYSMSGP.
Remove QUSRTOOL TAA members. Removes the TAA members from the QUSRTOOL source files. This saves space on the system because the product has all of the tools that were in QUSRTOOL.
Remove Source +++ Comments. Removes the source comments that are specially marked as +++ from different source types. This allows tools which are used as a base to code from (e.g. DMOSUBF) to have temporary comments relative to modification and then a simple command removes the temporary comments.
The Remove Source Members command removes members from a source file based on a number of retention days. The comparison may be made to the Create Date, the Change Date, or the Use Date. An ACTION parameter exists and defaults to *CHECK to provide a listing of what would be removed.
Remove system library list entry. Provides a method of allowing a user job to remove a library from the system portion of the library list. The Security Officer must describe the valid libraries to be removed in the RMVSYSLIBE data area in TAASECURE with the EDTCONARR command.
The Remove Trailing Nulls command will remove trailing nulls (X’00’) from an input variable and convert them to blanks (X’40’) values. The input variable may be up to 5000 bytes in length. The output variable must be 5000 bytes. A start position may be named. No embedded nulls are changed. Trailing blanks are ignored.
The Rename Generic Object command allows a rename of generic objects in a named library. The new generic name value must be less than or equal to the length of the existing generic name. Any characters in the name of an object after the generic name are carried over to the new name. A listing is produced including any errors found.
The Rename Generic Source command allows a rename of generic members in one or more source files in a library. A single source file, all source files, or special values for source file names such as *STD may be used.
The Rename IFS Authorities command allows you to change the authorities from one user to another for IFS objects. The default is for ACTION(*CHECK) which will not cause any changes, but a listing is produced describing the changes that would occur. Two exceptions exist that will prevent a change 1) if the user is the owner of an object, or 2) if the user is the Primary Group Profile of the object.
The Rename Primary Group Profile command uses the CHGPGP command to rename the Primary Group Profile of the IFS objects for a user. The To user becomes the new Primary Group Profile. The default is *CHECK meaning no changes would occur and a listing of the objects that would be changed is output. *CHANGE may be specified to change the Primary Group Profile attribute.
The Rename IFS with Translation command renames directories and files described in a CVTIFS outfile (*TYPE2). Renaming is done character by character for up to 10 different characters that may be replaced. Unmatched characters are not changed. RNMIFSXLT can be helpful when transferring IFS objects to different system types which have different naming conventions.
Rename message description. The command is useful if you write your own message descriptions and want to rename an existing message description.
The Rename Object Primary Group Profile command sets the PGP attribute of one or more objects to a new user profile. The PGP attribute is set by the CHGOBJPGP command. The default for RNMOBJPGP is for ACTION(*CHECK) which causes a listing of what would be changed. ACTION(*CHANGE) should be specified to change the attribute (set it to the new user profile).
The Rename User Profile command allows an existing user to be renamed to a different name. Owned objects, authorizations, authorization lists, spooled files, names within Job Descriptions, names within Job Schedule entries, and Directory entries are changed. Some restrictions exist and no values in user data or TAA objects are changed.
The Roll Dice command provides a game for the throwing of 2 dice. Each time the Enter key is pressed, a roll of the dice occurs. The display shows a picture of two dice and their values.
The Rotate List command allows a list to be passed to the command and returns an element by rotating thru the list. When the last element is returned, the next use of ROTLST will return the first element. This can be useful when dealing with a list of items which must be wrapped around.
RPG Alternate Lookup. This provides sample code for how to do a simple ‘hashing’ technique instead of an RPG Lookup operation. The intended use is for batch jobs which must summarize data into 2000 totals or less. This provides a much better performing solution than sorting the data, building an access path, or using a large array in an RPG program. The ANZRPGLKP command is provided to assist in determining the effectiveness of the technique.
The RPG Decimal subroutine provides an RPG solution for converting a left adjusted character field (with or without decimal position or separator characters) into a decimal field. Various validity checking options exist.
RPG code to Send a Message. The code uses the QMHSNDPM API. The sample code is intended to be copied into an RPG program. It contains a standard subroutine for sending messages. The message text is placed in an RPG array. The sample makes it easy to send a CPF9898 escape or status message. The sample source is provided in the QATTINFO member (no other source exists). For simple solutions see SNDESCMSG, SNDDIAGMSG, and SNDSTSMSG.
RPG Status Data Structure Definition. Provides an externally described file that can be easily used to define an RPG III or RPG IV data structure. This provides standard field names as well as the proper from/to positions.
RPG Validity Checking Technique. Describes how a sub program can be written to provide standard validity checking for an entry or update program. Provides a solution for displaying error text beyond a single line entry. The sub-program can be used for checking of a single record as well as providing a solution for providing referential integrity to ensure that data in related files is also kept synchronized.
Replace Command. Replaces an existing command by extracting all of the existing attributes (e.g. PGM) and re-creating the command. Useful for simplifying command re-creation when only the command definition source has changed. Copies any exiting authorizations to the new object.
Replace Display File. Replaces an existing display file by extracting all of the existing attributes (e.g. SHARE) and re-creating the file. Useful for simplifying file re-creation when only the DDS source has changed. REPLACE(*YES) is specified to allow copying of any existing authorizations.
The Replace Data Queue command re-creates a data queue with the existing attributes and authorizations. Because data queues may grow to be a large size, re-creating the data queue ensures the object is reset to its base size.
The Replace Duplicate Object command provides a method of replacing a set of objects that are duplicates in one library from a second library. For example, if one library has a subset of the objects in a product library and the product library is replaced, RPLDUPOBJ can refresh the subset library.
The Replace Edit Description command uses the outfile created by CVTEDTD to replace one or all of the Edit Descriptions (5-9) in QSYS. A specific Edit Description (or all) are deleted and then the values from the CVTEDTD outfile are used to create the new Edit Descriptions. The command is helpful in moving a standard set of Edit Descriptions to other systems.
The Replace Generic Display Files command allows the re-creation of generic display files or all display files in a library. The TAA Tool RPLDSPF is used to re-create each display file. It retrieves many of the existing attributes from the display file and then re-creates with the current attributes. By default, the same source member and file are used.
The Replace Generic Programs command allows the re-creation of generic programs or all programs in a library. The TAA Tool RPLPGM is used to re-create each program. It retrieves many of the existing attributes from the program and then re-creates with the current attributes. By default, the same source member and file are used.
The Replace Job Description Library command allows a replace of an existing library in one or more job descriptions with a different library name. The replace library takes the position in the library list of the library being replaced. RPLJOBDLIB can be useful if library names must be changed.
Replace Logical File. This is a replace facility after the DDS has been changed for a logical file. The file is named and the object is re-created with the new DDS. This includes multi-format files, join files, and multi-member files. The attributes of the existing object (e.g. SHARE) are extracted and used on the new object. Useful for re-create requirements.
The Replace Module command re-creates an existing module. The intent of RPLMOD is to provide a simple re-create when only the source statements have been changed.
The Replace Object command is designed to replace objects that are created from source. It uses several other TAA tools to provide a replace of Physical and Logical files, Display and Printer files, Commands, Modules, and Programs. RPLOBJ can run over a single object, generic objects, or all objects in a library.
Replace Physical File. This is a replace facility after the DDS has been changed for a physical file. The file is named and the object is re-created with the new DDS. An option allows the data to be copied with CPYF FMTOPT(*MAP *DROP). If dependent logical files exist, they are re-created at the same time with the RPLLF tool. No programs are recreated.
The Replace Program command re-creates an existing program using the parameters that are stored in the object. Most program types are supported including multi-module ILE programs. This simplifies the create process.
Replace Printer File. Replaces an existing printer file by extracting all of the existing attributes (e.g. SHARE) and re-creating the file. Useful for simplifying file re-creation when only the DDS source has changed. REPLACE(*YES) is specified to allow copying of any existing authorizations.
The Replace System Reply List command uses the outfile created by CVTRPYLE to replace the current System Reply List entries. All existing entries are deleted and then the entries from the CVTRPYLE outfile are added. The command is helpful in moving a standard set of Reply List entries to other systems.
The Replace System Values command uses the outfile created by CVTSYSVAL CMPSYSVAL(*YES) to replace system values. Some system values such as QDATE are bypassed as being unique to each system. Some system values such as QCONSOLE are non-changeable. The command is helpful in moving a standard set of System Values to other systems.
The Repeat Command command is primarily a testing aid and allows a command to repeated between 1 and 99999 times. RPTCMD can be helpful when stress testing a function.
The Resend all Messages command resends all messages that exist in the current programs message queue to the previous programs message queue. This bubbles up all messages. See the RSNLSTMSG command for resending the last message received.
Resend last message provides a simple solution in a CL program to resend the last message received in the program message queue to the calling program’s message queue. If an escape message is received, you may optionally resend a prior diagnostic message if it exists. Simplifies resending of simple messages such as completion messages from CRT commands or escape messages.
The Resend Message Key command resends messages from the job log (intended for low level messages). You must first run the RTVMSGKEY command (part of the RMVMSGKEY tool) to set a mark in the job log prior to running a function that produces low level messages. RSNMSGKEY may then be used to resend either a specific message ID or all messages from the RTVMSGKEY mark.
Restore All Changes. Restores all libraries on a tape using the RSTOBJ command. Designed for use with the SAVCHGOBJ or TAA tool SAVALLCHG command. Can be used on any tape where one or more libraries exist without having to know the library names. If the library does not exist on the system, a default version is created. A listing is provided with one line per library to assist in identifying problems.
Restore All Libraries. Restores all libraries on a tape using the RSTLIB command. Designed for use where a SAVLIB command was used to save one or more libraries by name (e.g. a special value like *NONSYS was not used). Can be used on any tape where one or more libraries exist without having to know the library names. A listing is provided with one line per library to assist in identifying problems.
Restore Any Library. Allows the system operator to adopt the security officers profile and prompts for the RSTLIB command. Useful when restoring an entire system or a new library to avoid exposures of the user who does the restore not being properly authorized to all objects. The user must be authorized to the TAARSTANYL authorization list.
Restore authorization list data. The companion tool is SAVAUTL. RSTAUTL may be used on the same system or another system to allow authorization list information to be reapplied from the information created by SAVAUTL.
Restore File. The RSTFIL command is intended for those security situations where the restore commands must be kept secure, but data files should be allowed to be restored. The intent is that the publicly authorized RSTFIL command would be used to restore data and source files to the RSTOBJ library. Programmers and operators must then use normal system security to copy the data to the required library.
The Restore Library to IFS command simplifies restoring a library from an IFS stream file such as was sent in an E mail attachment. The library must have been saved by the companion tool SAVLIBIFS or a SAVLIB command. The command does the following: 1) creates a save file in QTEMP 2) uses CPYFRMSTMF to copy the stream file to the save file 3) uses RSTLIB to restore the library. The library to be restored must not exist.
The Restore Many Changes command restores from a tape created by SAVCHGOBJ or TAA tools such as SAVALLCHG which uses SAVCHGOBJ. The command allows one or more libraries to be restored. See the companion command RSTALLCHG which allows a restore of all libraries from a tape with an optional list of excluded libraries.
The Restore Many Libraries command allows you to specify a list of libraries or generic names that should be restored from a tape saved by SAVLIB commands. It differs from the system RSTLIB command which allows only a single library to be named. It differs from the RSTALLLIB tool which restores all libraries from the tape.
The Restore Object from IFS command simplifies restoring objects from an IFS stream file such as was sent in an E mail attachment. The objects must have been saved by a SAVOBJ command such as the companion command SAVOBJIFS. RSTOBJIFS does the following: 1) Creates a save file in QTEMP 2) Uses CPYFRMSTMF to copy the stream file to the save file 3) Uses RSTOBJ to restore the objects to an existing library. See the companion tool SAVOBJIFS.
The Restore Objects to Save File command reads a tape saved by SAVLIB or SAVOBJ for one, many, or all libraries and restores the objects to the TAATMPLIB library for each library found. After each library is restored, a save file is created in a named library and the TAATMPLIB library is saved to the save file. The TAATMPLIB library is then cleared and the next library is processed.
Restore One Library. This is a front end to the RSTLIB command that eliminates most of the prompts. Useful for simple transferring of libraries.
The Restore Save File Member command provides a simple solution for restoring members from a save file. RSTSAVFMBR is a front end to RSTOBJ with fewer parameters, better defaults, and better error messages.
The Restore Save File Object command provides a simple solution for restoring objects from a save file. RSTSAVFOBJ is a front end to RSTOBJ with fewer parameters, better defaults, and better error messages.
The Restore TAA Stream File command is designed to restore the PF528 stream file containing a library for TAA tool source. The stream file is the standard name used when revised TAA source is sent to you via an E mail attachment. You must first copy the E mail attachment into an IFS directory. You may perform the copy by mounting the IFS through ‘Network Neighborhood’ (Net Server) or by FTP.
The Return Current Library command is intended for the case where you want to temporarily set the current library within a job. After retrieving the current value and setting your own value, resetting the current library is made complex by the fact the job may have had either a named current library or use *NONE (*CRTDFT is used). RTNCURLIB handles the resetting.
Return Library List. The RTVJOBA system command allows access to the current library list. The returned variable cannot be used directly with CHGLIBL because it expects a list and RTVJOBA has returned a string. RTNLIBL allows a simple replace with the retrieved variable rather than building up a command string and using QCMDEXC. Useful for working with RTVJOBA USRLIBL parameter.
The Retrieve Active Subsystems command retrieves the active subsystems on the system and returns them in a large variable. Each 20 byte entry is made up of the subsystem name and library. The number of active subsystems and the controlling subsystem and library are also returned.
The Retrieve All User command retrieves the exception libraries found in the SAVLIB LIB(*ALLUSR) help text for system libraries. Unique return parameters exist for # and Q libraries. The # libraries are not saved by SAVLIB(*ALLUSR). The Q libraries are saved by SAVLIB(*ALLUSR). This assists in the processing of commands that emulate the *ALLUSR function or the unique TAA *ALLUSR2 function.
The Retrieve Area Code command retrieves the description of an area code including the time zone, state, and up to 5 descriptions (such as city names). Only the area codes provided in PRTARACDE are supported (includes US, Canada, Caribbean, Samoa, etc).
The Retrieve ASP (Auxiliary Storage Pool) List command retrieves the number of ASPs on the system and a list of their numbers and device names. This allows for further processing of the ASPs by using the retrieved numbers or device names.
The Retrieve ASP (Auxiliary Storage Pool) Status tool retrieves the status and descriptive information about a single ASP. One or more return variables are provided.
The Retrieve Audit Model File command retrieves the model file in QSYS based on an entry type for a journal entry. Only the entry types associated with the T journal code (for Journal type = Audit) are supported.
The Retrieve Authority Source Description command translates the 2 character ‘Authority Source’ provided by the QSYRUSRA API or the TAA RTVOBJAUT command and returns a 30 byte text description. The description can be used to provide a meaningful value for how authority is determined.
The Retrieve Calendar Days command returns a large variable with the days of the year in CYMD format plus a digit representing the day of the week (Sunday = 1). Each entry is 8 bytes. Selection criteria exists for specific days of the week. RTVCALDAYS is useful when a list of days is needed.
The Retrieve Caller of a HLL tool is a program that can be called from any HLL program to determine the name of the program that called the current HLL program. A similar function is provided for CL programs by use of the RTVPGMNAM tool.
The Retrieve File CCSID (Code Character Set ID) command retrieves a summary of the CCSIDs specified for a data base file. CCSIDs are assigned to each character field in a file and normally all character fields will use the same CCSID. If different CCSIDs are used within the file, different processing may be required. RTVCCSID allows you to determine if a file uses a standard CCSID for all character fields and what the value is.
The Retrieve CCSID From PF command retrieves the CCSID from a physical file. If the file has multiple CCSIDs, TAA9896 is sent as an escape message.
The Retrieve Century command provides a solution for a sliding date window. The intent is that you would input a 2 digit year (such as 96 or 02) and be returned both a 2 digit century (such as 19 or 20) and a one digit century (such as 0 or 1). A sliding window is used based on 50 years in either direction from the current year. The function may used as a command, a sub program, or a subroutine in your program.
The Retrieve CLP Call command retrieves the attributes of parameters that are passed from a CALL command within CL source. Two arrays are returned. The first contains the variable names (or *CONSTANT) and the second contains a data structure of the attributes. Useful for working with the definitions used in a program.
The Retrieve CLP Variables command retrieves the variables and their attributes from CL program source. Two arrays are returned. The first contains the variable names and the second contains a data structure of the attributes. Useful for working with the definitions used in a program.
Retrieve class attributes. Retrieves the attributes of a class object as return variables to a CL program. Uses DSPCLS and CPYSPLF. Release dependent function. Useful for accessing existing class attributes.
Retrieve Command Attributes. Retrieves the attributes for a command as return variables to a CL program. Uses an API to access the information. Useful for accessing existing command attributes.
The Retrieve Command Parameters command retrieves an array of information where each element contains a data structure of the parameter attributes. The command is intended for use in programs where the attributes of the command parameters are needed. The source member is accessed. Not all parameter attributes are supported.
The Retrieve Command Source command retrieves information from a Command Definition object and generates source statements based on the definition.
The Retrieve Command Source 2 command is designed to retrieve the source for system commands. It differs from RTVCMDSRC which does not provide prompt text for system commands. In order to provide prompt text for keywords, the command help text is accessed. You must correctly perform the actions described in the prompt when RTVCMDSRC2 is used. Several restrictions exist.
The Retrieve Cancel Key command retrieves the action of the last system display function (including the command prompter) and returns the setting of the Cancel and/or Exit key. This allows a program using the display to determine whether the display was ended with the Enter key versus the Cancel or Exit key. The QUSRJOBI API is used to retrieve the information.
The Retrieve Column Heading command is a program that can be called (TAADBLRR) to retrieve the column headings for a field in a file. An externally described data structure is used to communicate with the program (TAADBLRP). The intent of the program is to allow a general purpose print program where neither the file nor the fields are known when the program is written.
The Retrieve Controller Description ASYNC tool retrieves information about an ASYNC controller. Because many parameters exist, 2 commands are provided (RTVCTLASC, and RTVCTLASC2). This provides the current information about the controller. The QDCRCTLD API is used to retrieve the data.
The Retrieve Controller Description Host tool retrieves information about a host controller. Because many parameters exist, 3 commands are provided (RTVCTLHOST, RTVCTLHOS2, and RTVCTLHOS3). This provides the current information about the controller. The QDCRCTLD API is used to retrieve the data.
The Retrieve Controller Description Local Workstation command retrieves information about a local workstation controller. This provides the current information about the controller. The QDCRCTLD API is used to retrieve the data.
The Retrieve Controller Description Network command retrieves information about a network controller. This provides the current information about the controller. The QDCRCTLD API is used to retrieve the data.
The Retrieve Controller Description Virtual Workstation command retrieves information about a Virtual Workstation controller. This provides the current information about the controller. The QDCRCTLD API is used to retrieve the data.
The Retrieve Current Member command retrieves information about the newest member (or generic member) in a data base file. This is based on the create date/time of the members. RTVCURMBR may be helpful when you want to process the most current member of a file and do not know the name of the member.
Retrieve Date. Retrieves the current or a specified date in a variety of formats as return variables to a CL program. Formats include the normal print version (e.g. Nov 2, 1993), TUE, Tue, Tuesday, Nov, NOV, November, the day of the week, the week of the year etc. Useful for CL programs which need to access a date.
The Retrieve Date Entry Description command is designed to bring back a description of how a job date should be entered when the date format and date separator may vary. The current job date format and separator are used to construct the description.
Retrieve Date 2. Provides an API solution (program interface) for retrieving a date in a variety of formats. An externally described data structure is used to return the formats. This is similar to the TAA Tool RTVDAT, but allows execution from any HLL program. The CRTRTVDAT2 command is available to provide for translation of the descriptions.
The Retrieve Date 3 command allows you to request a date such as the first Monday in October of a specific year and returns the actual date in CYMD format. A specific week or the last week of the month may be specified. The command is helpful when scheduling events.
The Retrieve Date 4 command is a subset of the RTVDAT TAA command. RTVDAT4 returns only the digit of the day of the week and the week of the year. The intent is to provide better performance than RTVDAT. Both return parameters should be specified for better performance.
The Retrieve Date 5 command allows an input of a one digit day of the week (1 = Sunday) and/or a 2 digit month (01 = January) and returns the spellings for the day and month. RTVDAT5 may be used following RTVDAT4 to return the spelling of the day.
The Retrieve Data Base File Attributes command retrieves basic file level information for either physical or logical files using the QDBRTVFD API. The optional return variables include such values as the file type (PF or LF), the type (data or source), the type of access path, the number of key fields, the use of externally described data, and the number of members.
The Retrieve Library Data Base File Members command returns counts of data files and members and source files and members in a library.
The Retrieve Data Base Override command retrieves the override values assigned to a data base file. The OVRDBF command is passed back in a large variable. RTVDBFOVR reads the spooled file created by DSPOVR. The command requires an upper/lower case English language system.
The Retrieve Data Base File by Relative Record command allows a retrieval of the contents of up to 10 fields from a record in a data base file using a RR number. Both character (up to 50 bytes) and decimal fields are supported. The command allows a general purpose approach that may avoid having to write a program.
The Retrieve Data Base Relations command retrieves the list of dependent files to a return variable. Only data dependencies are returned. The information is similar to DSPDBR, but operates using the QDBLDBR API to produce faster results.
The Retrieve DDM Attributes command retrieves the attributes of a DDM file. This includes such attributes as the Remote File name, Remote location name, and Remote network identifier. Only a file created by CRTDDMF may be used.
The Retrieve Decimal Data Area command retrieves the value of a decimal data area without knowing the length or decimal positions to a *CHAR LEN(17) variable. A minus sign may precede the value. A decimal format character will exist if decimal positions are defined for the data area.
The Retrieve Device Category command retrieves the category for a device. For example, the return category would be a value such as *DSP or *PRT which can then be used to gain other information about the device.
The Retrieve Device Display command retrieves information about a display device such as the type, model, and whether the current session is a passthru job.
The Retrieve Device Printer command retrieves information about a printer device such as the type, model, switch settings, and port.
The Retrieve Device Tape command retrieves information about a tape device such as the type, model, and resource name.
Retrieve Diagnostic Message. Provides a simple solution for retrieving the diagnostic message which immediately precedes certain escape messages. Both the escape and diagnostic message information is retrieved.
The Retrieve Directory Entry command retrieves a directory entry (see WRKDIRE) when only the name and address or just the name is known. This allows use of the return values to be used in other commands.
Retrieve Deleted Records. Retrieves the deleted records from a physical file. When a record is deleted, a flag is placed in front of the data. The operating system prevents any access. However, a SAVxxx command will save the information. RTVDLTRCD saves the data to a save file and then reads the save file to extract the deleted records. Useful for recovery.
The Retrieve Document Object command allows the retrieval of information about a *DOC object when only the system object name that exists in the QDOC library is known. The system object names may appear from a function such as when using the DSPOBJD outfile. These names do not relate to a user recognizable name. RTVDOCOBJ provides a translation from the *DOC object name to the information provided by QRYDOCLIB.
Retrieve Display File Attributes. Retrieves the attributes for a display file as return variables to a CL program. Uses an outfile to access the information. Useful for re-creating display files.
The Retrieve Display File Format command retrieves the number and names of the formats in a display file. A large return variable is provided with the format names and level IDs assigned to each format. The command can be used to help determine if one of the formats has changed since a program was last created that uses the file.
The Retrieve DST (Daylight Savings Time) Date command retrieves the actual dates that daylight savings time will begin and end for a Time Zone Description in a specific year. The system support for Time Zone Descriptions does not include actual dates of change. The TAA9893 escape message is sent if the Time Zone Description does not support daylight savings time.
Retrieve data area description. The command retrieves the attributes of a data area such as the type, length, and decimal positions.
The Retrieve Data Queue command retrieves the first entry in a data queue. Return values include the arrival date/time, sender ID, and the data. RTVDTAQ allows you to check if any processing should occur based on the arrival date and time of the first entry. The entry is not removed from the data queue. TAA9896 is sent as an escape message if no entries exist.
Retrieve Data Queue Description. Retrieves the attributes of a data queue into return variables. Uses the API QMHQRDQD.
The Retrieve Data Type Description command retrieves a description of the one byte code used by the system for data types such as A=Character and B=Binary. A 50 byte description is returned.
The Retrieve End of Month Date command returns the last date of the month in CYYMMDD format. The default is to retrieve the last date for the current month and year. A specific month and/or year (4 digits) may be used. A specific end day such as the last Friday may be named.
Retrieve field attributes. Retrieves the attributes of a field in a physical file or a single format logical file. Useful for determining if a field exists or its attributes.
Retrieve field information in an array. Retrieves an array of field names for a physical file or single format logical file. A corresponding multiple occurrence data structure is also returned. This provides a method of accessing the field attributes of a file.
The Retrieve Field Data command is a program (TAADBLSR) that may be called to retrieve the data for a field in a file. An externally described data structure (TAADBLSP) and a record image is used to communicate with the program. The intent of the tool is to allow a general purpose print program where neither the file nor the fields are known when the program is written.
The Retrieve Folder Object command allows the retrieval of information about a *FLR object when only the system object name that exists in the QDOC library is known. The system object names may appear from a function such as when using the DSPOBJD outfile. These names do not relate to a user recognizable name. RTVFLROBJ provides a translation from the *FLR object name to the information displayed by WRKFLR.
The Retrieve Format command retrieves information about the first or a named format in a data base file. Only the header type of information is retrieved such as the format text, format name, and number of fields. For detail field information, see the RTVFLDARR tool.
Retrieve Generic Member. Allows a simple approach for CL program processing of a generic group. The generic name is specified and the command returns the first member of the group. A subsequent use returns the next member of the group.
The Retrieve Generic Object command provides a simple method of processing a list of generic objects in a CL program. Each use of the command returns the basic information about a single object with the name, library, type, attribute, and text description. The list may be retained and processed multiple times.
The Retrieve Group Profile Indicator command retrieves a *YES/*NO for whether the specified user profile is a group profile. You must have *ALLOBJ special authority to use RTVGRPPRFI.
The Retrieve Hardware Resource command retrieves the name of a variety of hardware resources by type. A list of resource names (such as memory cards) may exist. The API QRZSCHE is used to return the information. For example, RSCTYP(*ECS) may return a value of CMN01 which is the name of the first and only resource assigned to Electronic Customer Support.
The Retrieve Holiday Date command retrieves the actual date of floating US holidays (where the date varies per year), such as Presidents Day, Memorial Day, Labor Day, etc. A specific year may be requested. The date is returned in YYYYMMDD format.
The Retrieve Home Directory command retrieves the home directory from the user profile for a named user. You must have *USE authority to the user profile to retrieve the information for a profile that is not your own. The RtvUsrInf API is used to extract the information.
The Retrieve Host Name command uses an IP address to retrieve the name of a host and up to 4 alias names. The command may be useful when the IP address is known, but not the system name. The ‘gethostbyaddr’ API is used.
The Retrieve IBM Profile command retrieves a list of system profile names to a large variable. By looping thru the list, you can quickly determine if a user profile name was shipped by system as part of the system.
The Retrieve IFS Entry Authority command returns the current users authority to an IFS object. The path name must be specified. Return values include the owner, authorization list, where the authority comes from (the named user or *PUBLIC), and individual authorizations. Authority checking by the system for IFS objects is not the same as checking object authority within libraries.
The Retrieve IFS Entry Description tool provides two commands for retrieving object information about an IFS object (the number of return parameters exceeds the limit for a single command). The information returned includes the owner, size, create date and other data that can be seen with the Display Attributes option from DSP/WRKLNK.
The Retrieve IFS Path command retrieves the IFS path name based on a ‘File ID’ such as found in a journal entry when an IFS object is journaled. An IFS journal entry does not contain the complete path name. The ‘File ID’ (16 bytes) is placed in the object name and library name (first 6 bytes). RTVIFSPATH allows a conversion from the ‘File ID’ to the actual path name. The API Qp0LGetPathFromFileID is used.
The Retrieve IFS Summary command retrieves summary information about the IFS. The outfile from the TAA command CVTIFS is used for the data. Count and size information is provided for the total IFS, user objects, and system profile owned objects. You may also name one profile to summarize information for.
The Retrieve ILE Module Attributes command retrieves the attributes for a module of an ILE program. Either a module number (default is first) or a module name may be specified.
The Retrieve ILE Program Attributes command retrieves the attributes from an ILE *PGM object. The RTVPGMA tool should be used to retrieve the basic program attributes. See the RTVILEMODA command for information about the modules.
The Retrieve Image Catalog Attributes command retrieves the general attributes about an image catalog. This includes the type, the status, the number of directories, etc. The QVOIRCLD API is used.
The Retrieve IP Interface command retrieves the information for an IP address from the QATOCIFC file in QUSRSYS and the QtocLstNetIfc API. A variety of return variables exist.
The Retrieve IPL Attributes command retrieves the default attributes that will be used on the next IPL. The values can be seen with the DSPIPLA display. The values may be changed by the system command CHGIPLA or if a manual IPL is performed.
The Retrieve IPL status command returns information about the current IPL such as the date and time, the controlling subsystem, and the status. RTVIPLSTS brings together in one command the important information about the current IPL.
The Retrieve IPL Time command retrieves the date/time the IPL started/ended, the number of seconds required to IPL, and the same information for the last powerdown. The end time of the IPL is not the time the system is fully operational as other jobs must be started such as TCP. RTVIPLTIM provides basic information about the time required.
The Retrieve Job API tool is a program that adopts the QSECOFR profile to allow retrieval from the QUSRJOBI API formats without having *JOBCTL special authority. The program is used by several tools that allow a user to display jobs that are not his own (the user cannot work with the jobs).
The Retrieve Job Attributes 2 command is similar to the system RTVJOBA command, but allows retrieval of the attributes for any job and supports more parameters. The system command is limited to the current job. Because the number of parameters exceeds the maximum that may be passed to a CL program (used for the command processing program), three commands are supported (RTVJOBA2, RTVJOBA2A, and RTVJOBA2B).
The Retrieve Job Completion tool retrieves the completion status for a job. Two solutions are provided: 1) RTVJOBCMPM (Retrieve Job Completion Message) and 2) RTVJOBCMPA (Retrieve Job Completion Accounting). Both solution provide for a delay time and a number of iterations to allow a program to wait for a reasonable time.
Retrieve Job Description. Retrieves the current values of a named job description as return variables to a CL program. Uses an API to access the information.
Retrieves the output queue of a job resolving any special values.
The Retrieve Job Performance command retrieves performance information about the current job. A ‘reset’ of the statistics must first be used for the job by RESJOBPERF or RTVJOBPERF RESET(*YES). Following the running of normal commands, RTVJOBPERF RESET(*NO) may then be used to retrieve the performance information that has occurred since the last ‘reset’.
Retrieve Job Queue Attributes. Retrieves the attributes of an job queue as return variables in a CL program. Also retrieves the number of jobs on the queue, the active subsystem name etc. Uses API QSPRJOBQ to access the information.
The Retrieve Job Schedule Entry command retrieves the information about a specific job schedule entry or the first or last entry for the same job name. Several optional return parameters exist.
Retrieve job start attributes. Retrieves the information into one or more return variables for how the job started. Any job (including the current job) may be specified. The variables include such things as the job queue, the subsystem, the job entry date/time, the job start date/time etc. Uses API QUSLJOB and QUSRJOBI to access the information.
Retrieve Job Status. Retrieves the job status of a specific user or job name. The type of status (e.g. *ACTIVE) may also be specified. Uses API QUSLJOB to retrieve the information. Useful for determining if a job is active, how much work a user has on the system, etc.
The Retrieve Job Status Loop command allows the current job to delay until another job is in a specified status. For example, if you submit a batch job, you may not want to continue in your program until the batch job is active or on an output queue.
The Retrieve Job Type Description command returns a 15 byte description for a job type such as BCH or SBS.
The Retrieve Journal Attributes command retrieves the attributes of a Journal such as the currently attached receiver name. The command may only be used in a CL program.
The Retrieve Journal Object Counts command retrieves summary information for different object types that are being journaled to a named journal. The API QjoRetrieveJournalInformation is used. The counts are kept by the system (the individual object information is not read).
The Retrieve Journal Receivers command returns a list of the journal receivers for a specific journal. This is known as the ‘receiver chain’. Each element in the list contains the receiver name and the library name. Other tools such as RTVJRNRCVA may be used to retrieve the attributes of an individual receiver. The QDBRTVFD API is used internally.
The Retrieve Journal Receiver Attributes command retrieves the attributes of a journal receiver as well as the number of entries, first and last sequence number, etc. The command may only be used in a CL program.
The Retrieve Key List command retrieves the basic access path information about a data base file and a list of the key fields with attributes. An API is used to allow faster access to key field information than using the DSPFD outfile function.
The Retrieve Lock Exclusive command allows you to determine if any job has an *EXCL lock on an object. Certain display functions such as DSPOBJAUT will fail if a *DTAARA object is locked by a different job to *EXCL. DSPPFM will fail if a member is locked exclusively. The API QWCLOGJL is used.
Retrieve Logical File Attributes. Retrieves the attributes for a logical file as return variables in a CL program. Uses an outfile to access the information. Simpler than accessing the attributes using DSPFD for a single file.
The Retrieve Logical File Member Description command retrieves information about a logical file member. The ‘based on’ PF information is retrieved for the first physical member. The QUSRMBRD API is used.
The Retrieve Logical File Source command retrieves the information from an existing logical file object and writes a DDS source member that attempts to emulate the original source that was used. The command has several restrictions. It is limited to simple logical files. Key fields described for the logical file are written to the DDS along with select/omit criteria.
The Retrieve Library List command returns a single variable which contains the libraries in the library list in the same sequence the system will check them when *LIBL is used. RTVJOBA returns portions of the library list, but not the complete list. The return variable is large enough to account for additional growth.
The Retrieve Library Size command retrieves the size and number of objects in a library. The library object is also considered. The command is slow running against a large library or a library with many source members.
The Retrieve Library Source Files command retrieves a list of source files in a library. The list is returned in a large variable.
The Retrieve Line Description ASYNC tool retrieves information about an ASYNC line. Because many parameters exist, 2 commands are provided (RTVLINASC and RTVLINASC2). This provides the current information about the line. The QDCRLIND API is used to retrieve the data.
The Retrieve Line Description Ethernet tool retrieves information about an Ethernet line. Because many parameters exist, 2 commands are provided (RTVLINETH and RTVLINETH2). This provides the current information about the line. The QDCRLIND API is used to retrieve the data.
The Retrieve Line Description Point to Point Protocol (PPP) tool retrieves information about a PPP line. Because many parameters exist, 2 commands are provided (RTVLINPPP and RTVLINPPP2). This provides the current information about the line. The QDCRLIND API is used to retrieve the data.
The Retrieve Line Description SDLC tool retrieves information about an SDLC line. Because many parameters exist, 2 commands are provided (RTVLINSDLC and RTVLINSDL2). This provides the current information about the line. The QDCRLIND API is used to retrieve the data.
Retrieve Last Change Information. The ‘last change date’ information kept on each source record (changed by SEU) is used. Up to five source records and the date they were changed are retrieved along with basic member information. In many cases the member level ‘last change date’ is changed (e.g. CPYSRCF) and it is desirable to know the last date of SEU changes. The DSPLSTCHG command is also included which provides a display of the same information.
The Retrieve Last Object command retrieves the last name of a generic name by object type. If you are naming objects using a generic technique, RTVLSTOBJ can assist in determining the last name assigned.
The Retrieve Last QHST command retrieves information about the last (current) QHST file in QSYS. The number of QHST files and their total size may also be retrieved.
The Retrieve Last Spooled File command retrieves information about the last spooled file written in the current job. This includes the name of the spooled file, the spooled file number, and the date and time of the create.
The Retrieve Member Description 2 command retrieves additional attributes that are not available on the system RTVMBRD command. This includes the initial number of records, increment number of records, maximum number of increments, and record capacity. 15 digit values are returned for size parameters.
The Retrieve Member Description 3 tool is designed for HLL program use to retrieve the description of a member. An externally described data structure is used to both pass the ID fields (file, library, and member) and return the description fields. The program TAADBKUR must be called and passed the externally described data structure. No command exists.
The Retrieve Member List command returns a large variable of member names that exist in a data base file. An API is used internally and the performance is very good when compared with the traditional method of creating and processing an outfile.
The Retrieve Member List command 2 returns a large variable of member information about the members that exist in a data base file. A data structure of information is provided for each member that includes the name, source type, text description, and last source change date. An API is used internally and the performance is very good when compared with the traditional method of creating and processing an outfile.
The Retrieve Member Statistics command retrieves data space activity that has occurred on a physical file member since the last IPL. The information provides statistics on the number of reads, updates, opens, access path builds, etc.
The Retrieve Member Summary command returns variables for such things as the number of members, the number of active records, and the data space size of all members for a data base file. Both physical and logical files are supported. RTVMBRSUM is designed for multi-member files. For single member files, the RTVMBRD and RTVLFMD should be used.
The Retrieve Menu Attributes command retrieves the attributes of a *MENU object. This assists in any application function where the attributes of a menu are needed. The function is release dependent and limited to upper and lower case English versions of the listing output.
The Retrieve Module Attributes command retrieves the attributes for a *MODULE object. The API QBNRMODI is used to retrieve the values. The command may only be used in a CL program.
The Retrieve Message Description command differs from the system RTVMSG command in that the message is retrieved as it exists in the message file. The system RTVMSG command returns the message with the replacement data included in the message text. RTVMSGD should be used when you want to see how the text appears in the message description.
The Retrieve Message Description 2 tool is similar to the system RTVMSG command, but allows a retrieve when only the message ID is known. This is desirable when the message file or message file library is not known. If the message file cannot be determined, TAA9892 is sent as an escape message. DSPMSGTXT has a similar function, but offers a display.
The Retrieve Message Description 3 command retrieves the format of the replacement data descriptions for a specific message ID. A large variable is returned made up of 20 byte elements for up to 49 replacement descriptions. Each element contains the type, the length, and the number of decimal positions if any. The QMHRTVM API is used.
The Retrieve Message File Attributes command uses an API to retrieve the attributes of a Message File.
Retrieve message queue attributes. The QMHRMQAT API is used to retrieve the attributes from an external message queue (not a program message queue). Return variables may be specified for such values as the number of messages, the delivery attribute, etc.
The Retrieve Message Type Description command retrieves a description of the 2 digit codes provided by the RCVMSG RTNTYPE parameter.
The Retrieve Masked Password tool provides a command to mask a password (CHGMSKPWD) and a command to retrieve a masked password (RTVMSKPWD). The password is translated to different characters and the positions are rearranged within a 256 byte field in the MSKPWDP file in TAASECURE. The tool may be used for a variety of needs such as with the TAA FTP commands which require a password be entered.
The Retrieve Month Date command allows a retrieval of the date in a month based on a day of the week and which week is desired. For example, you can determine the date of the 3rd Wednesday of a given month.
The Retrieve Month Name command retrieves the name of the month based on a plus or minus number of months from the current month. Different formats of the month name are provided. The system date is used to determine the current month (not the job date).
Retrieve Number of Active Jobs. Retrieves number of active jobs from one or more subsystems as return variables to a CL program. Uses the TAA tool CVTWRKSBS. Useful for determining if any active work remains in a subsystem.
Retrieve Network Attribute 2. Provides a simple API (program interface) for accessing a Network Attribute. The CPP can be called directly which allows a simple access to any Network Attribute from a HLL.
The Retrieve NetServer Attributes command retrieves attributes about the NetServer. Both current and pending attributes may be retrieved.
The Retrieve NetServer Statistics command retrieves the current statistics about the i5/OS NetServer such as the number of file opens and the average response time. The QZLSOLST API is used.
The Retrieve New Year command retrieves the first day of the year for any year in the range of 1600 to 4000. This allows other tools such as RTVDAT to operate on the same range of dates. Leap years are handled correctly.
The Retrieve Non-System command retrieves the libraries that are not saved by a SAVLIB(*NONSYS). Each entry returned has 2 libraries to allow for a range test such as QSYS00033 to QSYS00255. If only a single library like QSYS is not saved, the name is placed in both parts of the entry.
The Retrieve Next Day of Week command retrieves the date and the number of days from a date until a named weekday. For example, what is the date of the next Sunday. The date is returned in CYYMMDD format.
The Retrieve Next ID command is designed to return the next ID in a sequence. For example, if the last ID input is ABC, the next ID that would be returned is ABD. This allows the assigning of names based on the last ID that was used. This could be used for object or member names or for field names in a data base file. Numbers in the ID are optional.
The Retrieve Next Name command takes a name value such as ‘ABC0001’, adds 1 to the digit portion, and returns the next name ‘ABC0002’. The number portion of the name may contain 1-9 digit positions, but must be in the trailing position of the name. A rollover such as from a name ‘ABC9999’ causes an escape message. RTVNXTNAM may be used for objects, members, or your own internal naming convention.
The Retrieve Next Version command allows the input of a value such as ABC001, increments the digit portion and returns a value of ABC002. This can be helpful when an application is attempting to add another version.
Retrieve Object Authority. Provides a simple CL program interface to the QSYRUSRA API. The Y/N values are translated to X/blank which is the way authority is displayed externally. Additional return values are provided to allow a simple check to determine if the user has at least *USE or *CHANGE authority. Useful for checking authority in a CL program.
The Retrieve Object Authority 2 command retrieves the object authorities for a user of an object. Only the specific authorities for the user as seen on the DSPOBJAUT display are returned. Group authorities, Authorization List authorities, Program adopt, and *PUBLIC authorities are not considered.
The Retrieve Object Count command returns a count of the objects and types found, the first object and library found, and the number of libraries where the objects were found. Either a specific name, a generic name, or *ALL objects may be specified. It allows a CL program to determine information about objects before beginning any processing.
The Retrieve Object Description 2 tool is designed for HLL program use to retrieve the description of an object. An externally described data structure is used to both pass the ID fields (object, library, and object type) and return the description fields. The program TAAOBJWR must be called and passed the externally described data structure. No command exists.
The Retrieve Object Description 3 command provides a subset of the system RTVOBJD command. RTVOBJD3 is intended for use with multi-member data base files. The performance of RTVOBJD is slow on large member files because the size of all members must be added up. RTVOBJD3 returns a limited amount of information which does not include size.
The Retrieve Object Description 4 command allows you to retrieve the basic information about the first or only object of a specific name. The library and object type default to *ALL. A total number of objects that match the name is returned. If more than one object has the same name, messages are sent describing the first 30.
The Retrieve Object Journal Attributes command retrieves information about an object that is being journaled. Only *FILE (physical files), *DTAARA, and *DTAQ objects may be specified. The information returned includes whether the object is journaled, the journal name, images value, etc.
The Retrieve Object Lock command is designed to assist when an object is locked and you suspect there may be a single job holding one or more locks on the object. If only a single job holds one or more locks, return variables will describe the job and the strongest lock to allow a message to be sent. If locks exist from multiple jobs, the TAA9891 escape message is issued.
The Retrieve Object Library command returns the library name where a specified object was found. The libraries searched are specified in a library group as defined by the TAA LIBGRP tool. The intent of the tool is to be used as sub function when the library list cannot be used to identify all of the libraries where an object may exist.
The Retrieve Object List command provides a large return variable for a list of objects. The command is designed to replace the DSPOBJD outfile if minimal information per object is required. An API is used to retrieve the information to provide for better performance than DSPOBJD. 100 bytes of information is returned for up to 90 objects. If more than 90 objects satisfy the request, a second retrieve is needed.
The Retrieve Object Type Description command retrieves a text description of an object type. For example, *JOBD = ‘Job description’. The command may only be used in a CL program.
The Retrieve Object Version command allows you to retrieve the first or last version (based on the create date/time) when the same object name exists in multiple libraries. The command is useful when different versions are shipped in different libraries.
The Retrieve Output Queue Data Queue command retrieves the information about a spooled file that has just entered the RDY status in an output queue. A data queue must be created to receive the data queue entries. This allows a CL program to be written to perform a typical task such as moving spooled files in a RDY status to a different output queue.
The Retrieve Outfile command retrieves the model file and format for commands which create outfiles. Both system DSPxxx and TAA CVTxxx commands are supported. RTVOUTFILE may only be used with commands that use a single outfile. For example, DSPFD and CVTFD support multiple outfiles and are not supported. If a TAA CVT command is used, the outfile name used is also retrieved if one exists.
Retrieve Output Queue Attributes. Retrieves the attributes of an output queue as return variables in a CL program. Also retrieves the number of files, the writer name, the printer device name etc. Uses API QSPROUTQ to access the information.
Retrieve Physical File Attributes. Retrieves the current attributes of a physical file as return variables in a CL program. Uses an outfile to access the information. Simpler than accessing the attributes using DSPFD for a single file.
Retrieve physical file journal attributes. Uses API QDBRTVFD to retrieve the journal attributes of a physical file. Significantly faster than the alternative of RTVPFA.
Retrieve PF Source. Retrieves the source from an existing physical file object. The source is generated from the information in the object. Useful when the source has been lost or it is a file that has an object form only (e.g. a system model file used for outfiles).
The RTVPGMA command allows you to extract one or more parameters from an existing program into a CL program. This can be used for various functions in working with programs. An option exists to return the source information for single module ILE programs. See the RTVILEPGMA and RTVILEMODA commands for additional information about ILE programs.
The Retrieve Program Debug Attributes command retrieves a Y/N value about whether a program or module can be debugged by the ILE debugger. APIs for the ILE debugger are used to return the debug information.
Retrieve Program Name. In a CL program, you cannot easily determine the name of itself. The command provides a return variable of the program name that is running. It also provides a return variable for the program that called your program. Useful for determining ‘who you are’ and ‘who called you’ during the execution of a CL program.
The Retrieve Program Referenced Libraries command retrieves from a program type object the list of libraries used by externally described files when the program was created. The system DSPPGMREF command is used to determine the files used by the program. An option exists to add the libraries to the library list if they are not already on the list. RTVPGMREFL can be helpful when re-creating a program or module.
Retrieve Program Stack. Retrieves the program names that are in the program stack of the current job and returns them in a program variable. Use the API QMHSNDPM and QMHRCVPM. Useful for any function which needs to know what the current program stack is.
The RTVPGMSTK2 command allows you to extract one or more values from a program stack entry into a CL program. This provides such information as who the caller of your program is. You may ‘walk thru’ the stack by bumping the stack number each time you use RTVPGMSTK2. If the user has *JOBCTL special authority, the command may be used against any job.
The Retrieve Prompted Command command allows an input of a command string (such as just a command name), prompts for the command, and then returns the full command string including keywords without executing the command. Different formats are available such as for a command line or in a CLP source format. RTVPMTCMD is useful to applications that want to allow command input with prompting so the return command string can be run at a later time.
The Retrieve Product Description command retrieves a description of a licensed product such as 5761SS1. The description is returned in a 25 byte variable.
Retrieve Product Library. Retrieves one or both of the libraries that are in the Product Library portion of the library list. Can be used in conjunction with the CHGPRDLIB tool to swap the Product Libraries.
The Retrieve Printer Attributes command retrieves the attributes of a printer and the status of what it is printing. Because many attributes exist, two commands (RTVPRTA and RTVPRTA2) are used. Choose one or both to return the attributes you need.
Retrieve Printer File Attributes. Retrieves the attributes for a printer file to return variables in a CL program. Uses an outfile to access the information. Useful for recreating printer files.
The Retrieve Printer Overrides command retrieves the override values assigned to a printer file. The override command is passed back in a large variable so they may be used to override to a different file. Restrictions exist.
The Retrieve Previous Release command retrieves the ID of the previous releases in either a 6 or 9 byte character field such as VxRxMx or V0xR0xM0x. The N-2 release information may also be retrieved along with the earliest release that a save can run on. This allows a program to access the previous release ID on each release without changes.
Retrieve public authority. Retrieves the authority for the *PUBLIC user for a specific object. Separate return values exist for each type of authority (such as DATAREAD) or for the overall object authority (such as *USE). If the *PUBLIC user obtains the authority from an authorization list, the specifics from the authorization list are returned with an indication that the authorization list is the source.
The Retrieve Password Status command retrieves information about the status of a users password (not the password). RTVPWDSTS returns information that is not available using RTVUSRPRF. For example, you can determine if a password is valid for a profile.
The Retrieve QATT File Description (RTVQATTD) command returns the values needed to create a QATT source file. These are the name, record length, and descriptive text of the file.
The Retrieve QATT source files tool retrieves the names of the QATT files used in QUSRTOOL and the TAA Productivity Tools. Either a short list of files (as used by the TAA Tools) or the complete list of files is returned. A print command is also provided.
The Retrieve Qualified Name command extracts the command, qualifier, and label from a string. It also returns variables for whether a prompt character (?) exists, whether a leading comment exists, and the library where the command exists.
The Retrieve Record Lock 2 command retrieves counts of the record locks held and waiting for a job. The system CHKRCDLCK command only checks for locks within the current job. Some users would consider it an error to end a job that is holding record locks. RTVRCDLCK2 allows the ability to check for this condition.
The Retrieve Registration Information command retrieves information as displayed with WRKREGINF. RTVREGINF retrieves information for one exit point. The Retrieve Server Authentication Entries (QsyRetrieveServerEntries) API is used.
Retrieve Release ID. Retrieves the information about the release (e.g. V2R1M0) in various formats. Also retrieves the information about the current TAA update. Useful for a simple access to a displayable form.
The Retrieve Relative Month command will calculate and return three data values based on the date specified in the DATE parameter, offset by the number of months in the RELMTH parameter.
The Retrieve Remote Journal Attributes command returns information for a single remote journal. The command runs on the source system and the source journal must be specified. If no relational data base entry and no target journal is specified, the information for the first remote journal is retrieved.
The Retrieve RPG Call Parameters command returns the fields and their attributes that are passed on a specified Call within RPG source. Useful for determining if the correct parameter list is being passed.
The Retrieve RPG Fields command returns the fields defined in an RPG source member. The source may contain up to 1998 field definitions. Externally described data and /COPY functions are supported. Some restrictions exits.
The Retrieve RPG Parameters command returns the fields and their attributes for the parameters that are passed into an RPG program (PLIST *ENTRY parameters). The source member must be specified. Useful for determining if the correct parameter list is being passed.
The Retrieve Reply List Entry command retrieves the attributes of a specific System Reply List Entry based on a Sequence Number. Because the command returns variables, it may only be used in a CL program.
Retrieve Save File Description. Retrieves the important information about a save file into CL return variables. Allows a special message to be monitored for when no records exist. Useful for determining what is in a save file.
The Retrieve Submitted Command command retrieves the command that was submitted by a SBMJOB. The job may be on a job queue, be active, or have completed as long as DSPJOBLOG can be used. The command for the first ‘Request’ type message is returned. Several restrictions exist.
The Retrieve Submitted Job command returns the job identification of the job that was submitted by a SBMJOB command. RTVSBMJOB must immediately follow a SBMJOB command so that the system message sent by SBMJOB can be properly retrieved. RTVSBMJOB is helpful when the specific submitted job must be referred to at a later point.
The Retrieve Subsystem Batch Status command is intended to be an assist in determining if any batch jobs are active in a subsystem. Return values provide information on the number of active jobs, the number of batch jobs, and the number for typical status types such as that caused by DLYJOB. A supplied print command can be used to help determine the effectiveness of RTVSBSBCH.
Retrieve Subsystem Description. Provides return variables for information about the subsystem such as its status (active or inactive), the number of jobs active, and the detail information about the first 3 pools (ID, name, pool storage, and activity level).
The Retrieve Subsystem Pool command uses the number assigned to a subsystem pool to retrieve the corresponding system pool number when the subsystem is active. This is the same information as seen on WRKSBS.
The Retrieve Sign Position command allows input of a zero decimal position field and returns a *CHAR LEN(1) value for the low order digit. The low order digit will be a zoned value. RTVSGNPOS is useful when attempting to convert a negative decimal value to a character value.
The Retrieve SMTP Attributes command retrieves information based on a user ID about SMTP (Simple Mail Transfer Protocol). The QATMSMTPA file in QSYS is used. RTVSMTPA may only be used in a CL program.
The Retrieve Start of Month Date command retrieves the date for the first specified day of the month. For example, you can determine the date of the first Monday of the month. The date is returned in CYYMMDD format.
Retrieve Special Authority. Provides a simple solution for retrieving one or all of the special authorities from a named profile. Uses RTVUSRPRF to access the information. Useful in determining whether a user is authorized to perform a function before the function is attempted. Does not include any adopted authority.
Retrieve Spool Attributes within a printer file. The TAA tool RTVPRTFA retrieves the attributes unique to a printer as return variables in a CL program. RTVSPLA retrieves the spooled file attributes (e.g. OUTQ) within a printer file. This differs from TAA tool RTVSPLFA which retrieves the attributes of a spooled file. Uses an outfile to access the information. Simpler than using DSPFD when only a single file is needed.
Retrieve Spooled File Attributes. Retrieves the spooled file attributes as return variables in a CL program. Because the command is limited to 40 parameters, a second command RTVSPLFA2 is also provided. Uses API QUSRSPLA to access the information. Useful for determining the attributes of a spooled file.
Retrieve Spooled File ID. Provides a method of determining the ID of a spooled file when only part of the information is known. For example, you can determine the spooled file number when you know the name of the spooled file and that it is the last version. An alternative method of accessing the assigned ID from the file feedback area is also described. Uses the API QUSRSPLA to access the information.
The Retrieve Spooled File ID 2 command is intended for the situation where you need to know the spooled file name and number of the last spooled file in a job and you do not know the name of the spooled file. The return variables may then be used with commands such as RTVSPLFA to determine other attributes or DUPSPLF to duplicate the spooled file.
The Retrieve Spooled File Information command provides a fast method of determining the number of spooled files for one or all users. The QSPSPLI API is used.
Retrieve spooled file override. Retrieves most of the current attributes of a spooled file and returns the OVRPRTF command ready to be executed using QCMDEXC. The command is useful when a spooled file must be copied and then re-printed.
The Retrieve Spool Size command retrieves the number of members and their size from the QSPL library. The number of members with and without data are also retrieved. A member may exist that does not hold any spooled data as the system tries to limit the number of members that must be created.
The Retrieve SQL Package Attributes command retrieves basic information about an *SQLPKG object type. The spooled file from PRTSQLINF is used to access some of the information. Only lower and upper case English is supported.
The Retrieve Source Change command retrieves the number of source statements that have been changed in a source member since a specified date. The most current change date and the oldest change date are also returned.
The Retrieve Source Statement command allows a retrieve of a single source statement from a source member based on a relative record number or an argument to be scanned for. This allows a CL program to make a determination about a statement in the source.
The Retrieve Source Type command retrieves the name of the associated source file by using a source type such as RPG, CLP, etc. Some valid source types do not have a corresponding source file in which case *NONE is returned. The command can also be used to ensure a valid source type.
The Retrieve Service Program Module Attributes command retrieves the attributes for a module of a Service Program. Either a module number (default is first) or a module name may be specified.
The Retrieve Service Program Attributes command retrieves various return variables about a *SRVPGM object type. The API QBNRSPGM is used to retrieve the values. The command may only be used in a CL program.
The Retrieve Storage Pool command retrieves the information about a storage pool. Either a shared storage pool name or a pool ID must be specified. Various return parameters exist. The QWCRSSTS API is used.
The Retrieve Server Authentication Entry retrieves information for an authentication entry (added by ADDSVRAUTE). CCSID, User ID, and ‘Password specified’ values are returned. You must have both *ALLOBJ and *SECADM special authority to use RTVSVRAUTE.
The Retrieve System Description command retrieves information about the system such as the serial number, system type, model, feature code, feature group, number of processors, system name, etc.
The Retrieve System Date command is designed for situations where the system date format is not known and could be Julian. RTVSYSDAT returns a CYMD value for the current date using the API QWCRSVAL. It also returns the system date in job date format.
The Retrieve System Partition command returns the total number of partitions on a system and the current partition. The command is useful when dealing with LPAR systems.
The Retrieve System Security command retrieves the overall system security values including the current and pending security level, current and pending password level, whether changes can be made to security system values, whether to allow digital certificates to be added, and whether the service tools password can be changed.
The Retrieve System Status command retrieves system level information such as is found on the WRKSYSSTS display along with other values that represent the status of the system.
The Retrieve System Value Attributes command retrieves the attributes of a system value including the group (such as *SYSCTL), the type, the length, and decimal positions.
Retrieve System Value 2. Provides an alternative method of accessing a single system value. The command interface is not of particular value, but the CPP can be called directly which allows a simple access to any system value from a HLL.
Retrieve System Value 3. Provides an API (program interface) that accesses an externally described data structure containing commonly used system values. This includes the system date (as CYYMMDD and in system format), system time (as 6 or 9 bytes), serial number, model, date and time editing characters, currency symbol, and the network attribute system name.
The Retrieve System Value 4 command is an alternative method of accessing a single system value. It differs from RTVSYSVAL2 in that the return variable allows for 5000 bytes instead of the 900 supported by RTVSYSVAL2. The command interface is not of particular value, but the CPP can be called directly as an API which allows a simple access to any system value from a HLL.
The Retrieve TAA License command retrieves some of the important information from the TAALICENSE and TAACTL data areas in TAATOOL.
Retrieve tape ID. The command retrieves the heading information from a tape with return variables such as Volume ID, Owner, Density, etc.
The Retrieve Tape Label command retrieves information about a mounted volume and the first file (if any). This can be used to determine such information as the volume ID, the owner, the density, the name of the first file on tape, the date it was written, and the expiration date. The QTARTLBL API is used.
The Retrieve TCP Stack Status command retrieves TCP information for IPv4 and IPv6. Status information such as whether TCP is active or inactive is available for both IPv4 and IPv6. Starting and ending information is also available for IPv4.
Retrieve Time Stamp. Retrieves the current date and time in a variety of time stamp formats as return variables to a CL program. Useful for placing a timestamp in messages. None of the formats matches the data base Z type formats.
The Retrieve Time Stamp 2 command retrieves a 26 byte time stamp that is intended to be written to a data base Z type (Timestamp) field. The Timestamp data type has a required format of yyyy-mm-dd-hh.mm.ss.nnnnnn. The value returned will be unique across the system and will be ‘greater than’ the previous returned value.
The Retrieve Time Zone Description command retrieves information about a specific time zone description. This allows a program to process what is displayed by an option on WRKTIMZON.
The Retrieve Time Zone Time command retrieves the current date and time for a specified time zone. The day of week and offset from GMT may also be retrieved. Daylight savings time (DST) is considered if the time zone supports DST and the current date/time is within the DST start and end date/time.
The Retrieve TAA Tool Commands retrieves a list of commands for a named TAA Tool. The commands are passed back in a large variable which may then be used to perform other processing.
The Retrieve Translate Table tool provides a method of describing a standard translate table for system wide use and retrieving the value in a CL program. The data area is shipped with a value of QSYSTRNTBL in QSYS which is the name of the English version to fold lower to upper case. The value is retrieved by various TAA Tools to allow a translation to occur.
The Retrieve User Index Attributes command retrieves the attributes of a user index. Any user index may be retrieved from (not just those created by the TAA CRTUSRIDX command). The QUSRUIAT API is used.
The Retrieve User Profile 2 command allows a user to retrieve basic information about a user profile even though he does not have *USE authority to the profile. The user must be authorized to the TAARTVUSR2 authorization list to use the command. The command avoids the authorization problem caused by the fact that CRTUSRPRF defaults to AUT(*EXCLUDE).
The Retrieve User Space command allows the retrieval of up to 5000 bytes from a User Space. A start position may be specified so that multiple commands may be used to retrieve the data from a large user space.
The Retrieve User Space Attributes command retrieves the attributes of a user space. This can be helpful in determining the size and whether the space is set to auto-extend.
Retrieve User Space Entry. Provides a command interface to the QUSRTVUS API program to retrieve a list entry. Useful if processing a list entry in a CL program. A 1000 byte return variable is returned. You must substring into the variable to extract the information desired.
Retrieve User Space Initialization. Provides a command interface to the QUSRTVUS API program. The program returns variables to a CL program that are ready to use for the retrieve of the list information. The return variables can be used as input to the RTVUSRSPCE command or to a HLL program.
The Retrieve User Text command retrieves a user text description based on a user profile name. The command is useful if additional information is stored in the text description of the user profile or as a sub function when just the description is needed. The user of the command does not need to be authorized to the user profile. Only the text description is retrieved.
The Retrieve Universal Time command retrieves the coordinated universal date and time (UTC). UTC is based on an atomic clock with leap seconds added at irregular intervals to synchronize with the earth’s rotation. It may be used interchangeably with Greenwich Mean Time if sub second precision is not required. UTC may be useful when dealing with data from around the world.
Retrieve value attributes. Retrieves the attributes of a value that is up to 50 bytes long. Return variables include such things as the length of the data, whether only digits exist, whether digits and a decimal format exist, or whether the value is a valid name. You may optionally search for a specific character.
The Retrieve Virtual Tape Resources command retrieves the list of virtual tape resources, the status of each, and a count of how many exist. The names and status of each of the resources are passed back in a 1000 byte and 1200 byte variables where each resource name is 10 bytes and each status is 12 bytes.
Retrieve Work Station Attributes. Attributes such as the current device type can be retrieved. Uses the file feedback area in a program to access the information. Allows the program to condition operations before opening the real file.
The Retrieve Writer Status command retrieves the current status of a writer. Various attributes of the writer and of the current spooled file being written may be returned. The QSPRWTRI API is used internally.
The Run CPU command is intended as a testing aid to allow a batch job to use the CPU for a number of seconds. RUNCPU submits a batch job that loops and periodically checks the time of day to determine if the job should end. This causes the CPU to be active and keeps the job in a RUN status (as seen by WRKACTJOB).
The Run I/O command is a testing aid to submit a batch job to perform a series of writes to a data base file in QTEMP. This can assist in testing system performance by various tools that need to work with data base activity.
The Run Menu Command command provides the functions of QCMDEXC with additional functions provided by the QCAPCMD API. The additional functions include: 1) Prompting for the command on missing required parameters or some invalid entries and 2) Limited user checking. The command can be useful when attempting to simulate a command line on a menu.
The Run TAA Builder (RUNTAABLDR) command compiles the builder program referenced in the BUILDER and LIB keywords and then runs that builder. The builder will create a tool in the TAATOOL library.
The Revoke Duplicate Authorizations command provides a method for checking and revoking duplicate authorizations such as a specific user has *CHANGE authority as well as the *PUBLIC user to the same object. Group profiles and authorization lists are also considered. By default only a check occurs which produces a listing (no authorizations are changed).
The Revoke Duplicate IFS Authority command checks or revokes duplicate authorities to the *PUBLIC user of IFS objects. You must first run CVTIFSAUT to create an outfile of authorizations. If the authorization for a user is the same as the *PUBLIC profile, it is considered a duplicate (except for the owner). If the *PUBLIC user is specified as *AUTL, the authorizations from the *AUTL are used.
The Revoke IFS Authority command revokes the authorities of a specified user to IFS objects. The default is to ‘check’ rather than ‘revoke’. A listing is produced describing the results. The authority is not revoked if the user is the owner of the object or if the user is the Primary Group Profile. If the user is authorized via an Authorization List, the Authorization List is not changed.
The Revoke IFS Primary Group Profile command sets the Primary Group Profile to *NONE for a specific user. This allows some cleanup of the IFS objects. The command defaults to ‘*CHECK’ and provides a listing of what would be changed if ‘*REVOKE’ had been specified.
The Revoke Object Primary Group Profile command sets the PGP attribute of one or more objects to *NONE. The PGP attribute is set by the CHGOBJPGP command. The default for RVKOBJPGP is for ACTION(*CHECK) which causes a listing of what would be changed. ACTION(*REVOKE) should be specified to revoke the attribute (set it to *NONE).
The Save Active tool provides a simple method of achieving a safe save-while-active backup. The system must be shutdown (to the restricted state) during the running of the SAVALLACT or SAVCHGACT commands. The actual downtime should be considerably less than for a normal save command because of the system save-while-active function.
Save All Changes. Saves all the changed objects in user libraries on the system. Similar to the system command SAVCHGOBJ with the addition of several useful functions. The SAVALLCHG command saves directly to tape. The SAVALLCHG2 command saves to save files in a specified library. The companion command SAVALLSAVF saves all the save files to tape.
Save authorization list data. The command is intended to assist in the situation where objects must be restored to a second system (or same system) that are authorized to authorization lists. SAVAUTL creates a library with one or more authorization lists and captures the objects that are authorized to the authorization list. The companion tool RSTAUTL is used on the second system.
The Save Change 23 command is intended to be used on a daily basis between a periodic use of a Save Option 21 that saves the entire system. SAVCHG23 saves 1) System values, 2) Reply list entries, 3) Edit descriptions, 4) Network Attributes, 5) Security data, 6) Configuration data, 7) Changes to objects in all user libraries 8) Changes to objects in system libraries that contain user data 9) Changes to DLO objects, and 10) Changes to IFS objects.
The Save Data Base Dependent LFs and Restore Data Base Dependent LFs commands provide a solution for the case where a logical file is built over a physical file in another library and a system restore is needed. SAVDBDLF must be run prior to the save of the system. RSTDBDLF is run after the restore of the system to restore the logical files. Access paths may be rebuilt. A few LFs are created, saved by SAVDBDLF, then deleted before RSTDBDLF is run.
The SAVE2 tool provides a menu of save functions that are similar to the system SAVE menu, but only for options 20, 21, 22, and 23. SAVE2 provides better function than the system menu. A starting date may be entered as well as a function that allows a start when batch work has completed. By default the TAA Tools of CHKSAVRST and PRTSAVLBL occur automatically.
The Save File Archive tool is a series of commands that allows archiving of save files. This provides an online solution for save files to allow a restore of saved information without having to mount media. The sub tools WRKSAVFOBJ and WRKSAVFMBR may be used to allow an option for restore rather than entering complex commands.
Save and Restore Interchange Data. Allows a simple method of interchanging data and source between systems without using save/restore. Provides simple specifications for multiple files and members. Not designed for high volume in any one member, but more for source and small data files. Useful for shipping source to a S/38 or to a release that is not supported by the Save ‘previous release’ function.
The Save Journal Receiver command saves all, active, or detached receivers for a specific journal. Saving an active receiver (not detached) is supported by the the system, but can make it awkward to restore.
The Save Library to IFS command simplifies saving a library to an IFS stream file in order to allow the stream file be used as an E mail attachment. The command does the following: 1) creates a save file in QTEMP 2) uses SAVLIB to the save file 3) uses CPYTOSTMF to copy the save file to the specified stream file. See the companion tool RSTLIBIFS.
The Save Library to Save Files command saves one or more libraries to save files in a specified library. Special values exist and libraries may be omitted. Save files are created if they do not exist using the name of the library to be saved. The intent of SAVLIBSAVF is to allow you to save to a library of save files that can then be backed up to media at a later time. The companion command DLTLIBSAVF will delete the created save files.
The Save Object to IFS command simplifies saving objects to an IFS stream file in order to allow the stream file to be used as an E mail attachment. The command does the following: 1) Creates a save file in QTEMP with the name of the library 2) Uses SAVOBJ to the save file 3) Uses CPYTOSTMF to copy the save file to the specified stream file. See the companion tool RSTOBJIFS.
Save One Library. A shorthand command for SAVLIB to save a single library. A minimal of prompts appear with different defaults for SEQ and CLEAR. Useful for minimizing keystrokes for simple save requirements.
The Saved Owned Objects command saves objects owned by a specific user from a named library. A list of object types may be named. You must have *SAVSYS special authority to use SAVOWNOBJ.
The Save and Receive Library with FTP command is designed to simplify receiving a library from another i5 System. The SAVRCVL command saves the library to a save file in QTEMP and transmits the save file using FTP.
The Save and Restore ASP command allows a library to be saved and restored from one ASP to another. Both named and numbered ASPs are supported. An option exists to delete the existing library and must be used if the same library name is used for the restore library. A permanent library must be used for the creation of a save file used to save the library to and restore from. The save file is deleted if SAVRSTASP completes successfully.
The Save and Restore Job Queue tool supports two commands to provide for a save and restore of a job queue. CVTJOBQ2 creates an outfile of information about the jobs on a job queue. The file can be saved and restored to the same or a different system. The SBMJOBQ2 command may then be used to read the outfile and perform a SBMJOB for each job found in the outfile. Some restrictions exist.
The Save and Send Library with FTP tool is designed to simplify sending one or more libraries to another i5 System. Your objects should be placed in unique libraries. The SAVSNDL command saves your library to a save file and the save file is transmitted using FTP. On the remote system, use RSTSNDL (part of the SAVSNDL tool) to restore the library.
The Save and Send Member with FTP tool is designed to simplify sending a member, generic members, or all members (from the same file) to another i5 System. Either a source or data file may be used. The SAVSNDM command saves one or more members to a save file and the save file is transmitted using FTP. On the remote system, use RSTSNDM (part of the SAVSNDM tool) to restore the member.
The Save Source Files command allows a save of all source files in one or more libraries to tape or all source files in a single library to a save file. The system save commands only allow a save of *FILE objects and do not allow the saving of just source files.
The Save System in Batch command is designed to allow you to run backup functions in batch that require the restricted state. This includes Save the Entire System (Option 21), Save System Data (Option 22), and Save User Data (Option 23). This allows scheduling of these functions using the Job Scheduler or the SBMJOB SCDDATE/SCDTIME function. Both tape and virtual tape are supported.
The Save System Information 2 command is a front end to the system SAVSYSINF command. SAVSYSINF saves a subset of the system data saved by SAVSYS and can be used after restoring a SAVSYS version. SAVSYSINF2 is preferable to the system function because SAVSYSINF2 runs SAVSYSINF and then updates a data area in TAASECURE. This provides a version of the save information which would be lost if the last SAVSYS was restored.
The Save TAA Tool function is intended for those users who want to use the TAA Productivity Tools during a disaster recovery. The tool provides a method of saving the TAATOOL and TAASECURE libraries to save files in a special backup library so that the backup library can be installed early during a disaster recovery.
Save Data Base File While Active. Allows a technique to provide backup even though the file is being used 24 hours a day. Requires journaling be used. Provides some benefits that the system save-while-active function (on the SAV commands) do not.
The Submit Check of Active Job command is intended for the case where a job should either 1) Not run longer than n seconds or 2) Be running after n seconds. A message is sent to a specified message queue if the status is not what is requested.
The Submit FTP Command command submits a single command to run on another System i that is connected via FTP. It could be another LPAR partition on the same physical hardware. Like SBMNETJOB or SBMRMTCMD, SBMFTPCMD provides a simple method of submitting a job to another system, but uses the more popular FTP protocol.
The Submit Job Schedule Entry command submits one of the job schedule entries immediately. The job schedule entry is not changed. This allows a batch command interface instead of Option 10 (Submit immediately) from the WRKJOBSCDE display.
Submit Job 2. SBMJOB2 allows a submit where most of the parameters default to *JOBD rather than *CURRENT. It allows system operators to use standard job descriptions to submit work without worrying about the environment of their own job. SBMJOB3 allows a submit where even the command is stored in the JOBD. Useful for simplifying the system operator function for submitting work.
Submit Parameters. Allows the storing of command parameters with the source member. For example, the USRPRF option on CRTxxxPGM can be specified in the source of the program. The parameters must be specified according to a convention. Works in conjunction with a user defined PDM option or the Programmers Menu to submit a special program. An option exists for deleting objects before attempting the create.
Submit PDM Overrides. Allows PDM to be used when an override is needed during object creation. The most typical use of this function is when a S/36 group file function is used with externally described data. For example, the system will allow the creation of a file name with a period within the name (e.g. PAY.ABC), but RPG will not allow the same name.
The Submit Previous command is intended for use on the system command entry display where you have executed a command and now want to submit the same command (or a modified version) to batch using SBMJOB. SBMPRV extracts the last request message sent and prompts for the command on a SBMJOB prompt.
The Submit Time Job command is a compatibility command for a former version of a QUSRTOOL TAA command. The TAA Tool was removed when time dependent scheduling was added to the system. The new version of SBMTIMJOB provides a compatible command interface and does SBMJOB with SCDDATE and SCDTIME parameters. For new programs, SBMJOB should be used directly.
The Submit Time Job 2 command is a front end to SBMJOB that allows the same job to be submitted multiple times for a given day. A start and end time must be specified as well as a time interval in minutes.
The Scan Access Path command scans a library for access paths and determines if any key fields exist that match a key length specified on the command. SCNACCPTH is an option on the SCN2000 command and is intended for year 2000 considerations.
Scan All Distribution Lists will scan all distribution lists for a particular User ID. An output file is created listing all the dist lists in which the User ID was found.
The Scan All Data Areas command allows a scan for up to 20 different values for one, generic, or all data areas in a one or more libraries. This can be helpful when attempting to identify where values are located.
The Scan All Job Logs command will scan all or selected job logs for various criteria such as message IDs, message types, and a string of text. If a match is found, an abbreviated spooled file is written named JOBLOG. SCNALLJLG assists in finding information when the specified job log is not known. Selection criteria is a significant performance consideration if many job logs are scanned.
Scan All Source. Allows a simple specification to request the TAA tool SCNSRC. Submits a job to batch. Allows one or more standard named source files to be scanned for a string.
The Scan All Source 2 command will scan for up to 20 arguments in all source files in one or more libraries. Special values exist for the library name such as *ALLUSR. An omit list of libraries may also be named. The command is submitted to batch with JOBD and JOBQ parameters.
The Scan Audit Log command provides a different method of displaying or listing audit entries from the Audit Log data base file provided by the AUDLOG tool. In addition to standard selection fields such as date, time, user profile, etc, SCNAUDLOG allows a search on the entry data field. This can be particularly helpful for the ‘T’ Journal code (audit entries) where most of the data is in the entry data field.
The Scan CLP Command scans CL source members for up to 50 different command names. A display or listing is output. An outfile is optional. SCNCLPCMD offers better function that the system PRTCMDUSG command in terms of finding command usage. If an outfile is created, the model file in TAATOOL is TAACLTEP with a format name of CMDRCD.
The Scan CLP IF command is designed as an aid to assist in converting to the year 2000. It scans a member, generic members, or all members in a file of source type CLP, CLMOD, or CLLE for the use of a specified length of variables (6 is the default) that are used in some form of greater or less than comparison on any IF commands. A spooled file of the statements that match the criteria is produced.
The Scan CLP TAA Commands command scans the outfile created by CVTCLPCMD for TAA commands. CVTCLPCMD converts all commands found in a source file to one record per command in an outfile. SCNCLPTAA lists each command found in the file that exists in TAATOOL along with the source member and sequence number within the source.
The Scan Class Attributes command scans one or more Class Objects for attribute values. This acts as a simple query to determine the value of attributes of Class objects.
The Scan Command Attributes command scans one or more Command Objects for attribute values. This acts as a simple query to determine the value of attributes of Command objects.
The Scan Command Escape Messages command scans for a string of text in escape messages that are sent by a specific system command. Both the first and second level text are scanned. If the scan value is found in the second level text, the first level text is also listed. SCNCMDESC can be helpful when the text of an escape message is known, but not the message ID for a specific system command.
The Scan Command Keyword command scans source for the use of a specific keyword on a command. One, multiple, or all libraries can be scanned. All source files in each library are checked for the source types CL, CLP, CLLE, CL38, and CLP38. The output listing describes one line for each occurrence found.
The Scan Command Usage command uses the output from CVTCMDUSG (which uses the system PRTCMDUSG information) to determine which CL programs are using a specific command. The source is checked to see if it still exists and is flagged if it does not. An option exists to scan the source for a specific keyword used on the command.
The Scan Data Base File command scans one or more members of data base files for up to 20 strings. A listing is output with one line for each time one of the strings is found in a record. The relative record number of the record and the position where the string was found is described.
The Scan Data Base Field command allows a scan of a field in a data base file for *EQ, *LE, … *CT (contains). Up to 3 fields that help identify the record where a match was found may be listed. SCNDBFFLD provides a simple query of data.
The Scan Data Base Field 2 command is intended for name and address data base files when some pieces of a name and address are known but not all. SCNDBFFLD2 scans up to 5 character fields for up to 5 15 byte strings each. For example, if you know a string of letters from a name and a few from the address, SCNDBFFLD2 can help find the record.
The Scan Data Base File Record Length command scans one or more libraries for data base files that exceed a specified record length. The record length of a file is specified on the CRTPF command RCDLEN parameter for program described files or is the sum of the field lengths for an externally described file. An omit list of libraries may also be specified.
The Scan DDS Source command scans DDS source for various values such as a string of text in the Functions field such as the word ‘JOIN’. All selection criteria must be met to print a record. The command can be helpful when searching for some values that have been used previously.
The Scan Device Display Attributes command scans one, generic, or all display devices for attribute values. This acts as a simple query to determine the value of attributes of display devices.
The Scan Device Printer Attributes command scans one, generic, or all printer devices for attribute values. This acts as a simple query to determine the value of attributes of printer devices.
The Scan Display File Attributes command scans one or more display files for attribute values. This acts as a simple query to determine the value of attributes of display files.
The Scan Data command scans a character field or all character fields in a data base file for a value which may include wildcards. A spooled file is created which identifies each record containing the value, the field name, and the positions within the data where the value was found. Either character data or a hex value (X’xxxx’) may be scanned for.
The Scan Data Area command scans a data area for a string. This can be helpful if data areas are used to store user values and a search technique is needed. A value is passed back for where the string was found. The command may only be used in a CL program.
The Scan Data Queue command scans the entries in a data queue for a value. Both the scan value and the entry are converted to upper case before scanning. A listing of the entries containing the value is optional. An option also exists to send an escape message if the scan value is not found.
The Scan Data Queue Attributes command scans one or more Data Queues for attribute values. This acts as a simple query to determine the value of attributes of Data Queue objects.
The Scan Data Queue Maximum Length command scans one or more libraries for data queues that are defined with a maximum entry length that exceeds a specified value. The maximum entry length of a data queue is specified on the CRTDTAQ MAXLEN parameter. An omit list of libraries may also be specified.
The Scan Duplicate Records command is intended to assist you in identifying duplicate records in a data base. For example, different spellings of a name or address may cause multiple records for the same individual or company. Command options on SCNDUPRCD allow you to specify how to determine a possible duplicate group. It is expected that you will need to try various options to determine what best fits your situation.
The Scan and Extract Data command scans a string of data for a value and returns the first n bytes prior to a blank after a successful scan. For example, if you are scanning message text, you might want the value after the word ‘library’.
The Scan Extracted Message File tool is a series of commands that let you build a file of messages and then scan for a value. This can be helpful when you have seen a message containing a value such as ‘authenticate’, but no longer have the message ID to help determine the full text of the message. You may scan either the first or both the first and second level text.
The Scan Field Type command scans data base files in one or more libraries for one or more field types. For example, you can determine which files have field types for date (L), timestamp (Z), variable length (W), or BLOB (1).
The Scan Generic Source command scans generic members in a source file, all source files in a library, or a subset of the source files in a library. Up to 20 arguments may be scanned for. APIs are used to access the source files and members. This allows a fast method of finding all occurrences of up to 20 strings in multiple members.
The Scan Generic Source Description command provides a simple display or listing of generic source members. One line per member appears. Either a single source file, all source files, standard source files, or the QATT source files in a library may be requested.
The Scan IFS command scans one or more stream files for an argument. If the argument is found anywhere in the stream file, a line is listed identifying the IFS object. SCNIFS assists in searching for values in the IFS.
The Scan Job Description Attributes command scans one or more job description objects for attribute values. This acts as a simple query to determine the value of attributes of job descriptions.
The Scan Job Log command is intended to ‘net out’ a job log to allow a review by selection criteria. It allows a display or listing of a subset of the messages from a specific job log. The selection of messages may be done by a list of message IDs, message types, date/time range, severity, or by scanning the message text.
The Scan Job Queue Attributes command scans one or more Job queue objects for attribute values. This acts as a simple query to determine the value of attributes of Job Queues.
The Scan Logical File Attributes command scans one or more logical files for attribute values. This acts as a simple query to determine the value of attributes of logical files.
The Scan Library List command scans source to help identify any changes that must be made due to the V5R1 system change that increased the number of libraries from 25 to 250. Different scans are performed to help identify where you have used functions that may need to be changed.
The Scan Member Attributes command scans one or more data base members in a library for attribute values. For example, you can scan for the number of members with more than 1000 records or all members that have a keyed access path. This acts as a simple query to determine the value of attributes of members.
The Scan Message Queue command scans, one, generic, or all message queues in one or more libraries for up to 20 different arguments against the message text of the messages. A listing is output of the messages that match at least one of the arguments.
The Scan Message Queue Attributes command scans one or more Message Queues for attribute values. This acts as a simple query to determine the value of attributes of Message Queue objects.
The Scan Object Description Attributes command scans one or more objects for attribute values. This acts as a simple query to determine the value of attributes of objects.
The Scan for OPNQRYF command scans a specified source file for the use of OPNQRYF. SCNOPNQRYF is an option on the SCN2000 command and may be used for year 2000 considerations. The scan may be for a single member or a generic member name. A spooled file is created with one line for each statement that contains the string ‘OPNQRYF’.
The Scan Output Queue command scans for a spooled file name, generic name, or all spooled files in an output queue for 1 to 20 arguments. A spooled file is output with the results including the spooled file name, line number, and the data for each successful scan.
The Scan Output Queue Attributes command scans one or more Output Queues for attribute values. This acts as a simple query to determine the value of attributes of Output Queue objects.
The Scan Physical File Attributes command scans one or more physical files for attribute values. This acts as a simple query to determine the value of attributes of physical files.
The Scan Program Attributes command scans one or more programs for attribute values. This acts as a simple query to determine the value of attributes of program objects.
The Scan QHST command scans QHST information for a string of characters. You must first convert the QHST information using the CVTQHST2 command of the DSPQHST2 tool. Selection of which messages to scan may be made on a date range, Job, User, Job number, and Message ID. The scan occurs on the first level text and the message data of the each message.
The Scan RPG Compare command is designed as an aid to assist in converting to the year 2000. It scans a member, generic members, or all members in a file of source type RPG, RPGMOD, or RPGLE for the use of a specified length of fields (6 is the default) that are used in some form of greater or less than comparison. A spooled file of the statements that match the criteria is produced.
The Scan RPG Edit Code command scans RPG source for the use of one or more edit codes. A single member, generic members, or all members in a file may be scanned. The spooled output includes the member and statement for each edit code that matches.
The Scan RPG Field Names command scans any type of RPG source for one or more string of characters that are found within field names. The tool can be used as a Year 2000 assist to find the uses of strings such as DAT, DT, YR, YEAR, MON, MONTH or any general scan need. A single member, generic members, or all members in a file may be scanned.
The Scan RPG Field 2 command finds all references to a specified field name in a member, generic members, or all members in a source file. Only RPG source types (including RPGLE) are scanned for. If the specified field is found to change the data in another field, the derived field is also scanned for. The command is useful for determining the progress of a field and its data through a program.
The Scan RPG Field 3 command finds all references to a specified field name in a member, generic members, or all members in a source file that match a list of Operation Codes. A special Op code value exists to search for Operation Codes with Year 2000 considerations. Only RPG source types (including RPGLE) are searched for. Derivative fields are also considered.
The Scan RPG Edit Word command scans RPG source for the use of all edit words or a specific edit word. A single member, generic members, or all members in the file may be scanned.
The Scan Save File Attributes command scans one or more save files for attribute values. For example, you could scan for all save files that have more than 100 records. This acts as a simple query to determine the value of attributes of save files.
The Scan Spooled File command scans a spooled file for a string and returns a count of how many strings were found. Other return variables exist for the line of data where the scan value was found, the position within the line, and the page number. These values are returned as arrays of up to 100 values. Only the first time the string is found on a print line is considered.
The Scan Spooled File 2 command scans selected spooled files for a string and displays or prints the results. This allows searching for a string that exists in spooled files such as job logs. The QUSLSPL API is used to determine the selected spooled files.
Scan Source. Used for scanning a source file to look for a value string (e.g. where are all the uses of the ACCRCV field). Uses OVRDBF MBR(*ALL) and the QCLSCAN program. Useful for searching through source for specific values. The PDM FNDSTRPDM command provides a similar function, but produces more output.
The Scan Source SEU command scans one or more members in a source file for up 20 different arguments. If an argument is found, STRSEU is used on the member in either *CHANGE or *BROWSE mode. SCNSRCSEU simplifies making changes or reviewing source when several members have used the same string of characters.
The Scan Source Type command scans all the source files in a library (or libraries) of a specified type (or types) for a string (or strings). The command can be helpful when you want to scan for the existence of some string of data and you are not sure where the data may exist.
The Scan Source 2 command is the inverse of the SCNSRC command. SCNSRC2 scans for an argument and lists the member in a spooled file if the argument does not exist. One, generic, or all members in a source file may be scanned. An outfile is optional.
Scan TAA Tool Source. Scans the source in TAA tool source files (e.g. QATTCL or QATTCMD). Same function as SCNALLSRC except the source file names match those used by TAA tools. Useful for searching through TAA tool source for specific values.
The Scan and Update CL Source command scans one or all members of CL or CMD source for an argument and if found replaces it with a replacement value. The replacement value can be the same length, a shorter length, or a longer length. The source is reformatted similar to prompting in SEU.
The Scan and Update Data command scans a character field for a string and changes the string to a new value. Either character data or a hex value (X’xxxx’) may be scanned for. The command is useful for cleaning up data in a file.
The Scan and Update Hex 00s command replaces X’00’ values with blanks (X’40’s) and returns them in the same variable. The command can be useful when dealing with system data which frequently uses X’00’ in values. The variable must be declared as 5000 bytes.
The Scan and Update Source command allows a single member, generic members, or all members in a source file to be scanned for the value of a single statement and replaced by a single statement. The scan and replace values must exist in a separate source member which has only two statements. The entire statement is compared for a match (a scan does not occur).
The Scan and Update CLP Variable command allows a CL variable to be changed based on an existing pattern within the variable. The replace value must be the same length as the pattern to be replaced. The same pattern can be replaced if it occurs multiple times.
The Scan User Profile Attributes command scans one, generic, or all user profiles for attribute values. This acts as a simple query to determine the value of attributes of user profiles.
The Scan User Space command provides a method of scanning a user space for a value. A return parameter exists for the start position of the value. The function is supported on the DSPUSRSPC command. SCNUSRSPC may only be used in a CL program.
Scan a Variable. Command interface to the QCLSCAN program to allow simple scanning of a variable in a CL program.
Scan a Variable from the Right. Command interface to allow simple scanning of a variable from the right in a CL program. The default is to search for the first non-blank. A string of characters can also be specified. Useful for determining the actual of length of data in a field.
The Scan Variable Right 2 command scans a variable (up to 5000 bytes) for either the length of the data or for a string. SCNVARRGT2 can help determine the length of the data in a large variable or where a string of characters begins.
The Scan 2000 command is designed as an aid to assist in converting to the year 2000. It combines the use of the SCNCLPIF and SCNRPGCOMP for all source files in one or more libraries.
Scramble Data. The data in a field is scrambled (e.g. byte 1 becomes byte 4, etc.) and the bits are OR’d with a user specified unique code. An UNSCRAMBLE function also exists. Useful for masking data to be stored in the data base or transmitted.
The Security Log tool is designed to assist in auditing *ALLOBJ users. The SNDSECLOG command is intended to be used as the first command of an initial program for such a user. The command displays a screen and requires the user to enter a ‘purpose’ of why he is signing on. The command then sends a journal entry to the QAUDJRN journal with the ‘purpose’. Other SECLOG commands are used to convert and display the information.
Security Officer 2 Menu. Provides a menu for Assistant Security Officers that includes options such as Display User Profile (DSPUSRPRF2 tool), Initialize Password (INZPWD tool), Enable User Profile (ENAUSRPRF tool), and Vary Device On (Selectively prompted VRYCFG command).
The Select Data Base File command provides a display of designated files within a library and allows the user to select one. A return field describes the selected file. The command is designed for use as a sub function in an application where the user wants to select from a list of files. The DMOSELDBF command may be used to try a demonstration of the function.
The Select Data Base Member command provides a display of designated members within a file and allows the user to select one. A return field describes the selected member. The command is designed for use as a sub function in an application where the user wants to select from a list of members. The DMOSELMBR command may be used to try a demonstration of the function.
The Select Objects command provides a display of designated objects within a library and allows the user to select one. A return field describes the selected object and type. The command is designed for use as a sub function in an application where the user wants to select from a list of objects. The DMOSELOBJ command may be used to try a demonstration of the function.
The Select PDM Option command is intended for the WRKxxxPDM displays. A standard entry of SP is provided which will display a subfile of the available options in the QAUOOPT (or equivalent) file. The subfile appears in a window and options exist to Execute, Prompt, or Display the command details. A function key allows access to the TAA command ADDPDMOPT.
The Select Spooled File command operates from an interactive CL program and displays the spooled files for the current or named user and allows the selection of one spooled file. The ID information about the spooled file is passed back to the calling program. The QUSLSPL API is used to determine the spooled files.
The Set Message Queue to Break on Inquiry tool allows you avoid being interrupted by any messages sent to a message queue other than Inquiry messages. A SNDBRKMSG command can also cause a break, but can only be sent to a Work Station message queue. SETBRKINQ can avoid some needless interruptions.
The Set Daylight Saving Time command allows you to set the system for daylight saving time changes. The TAA function automatically changes the time of day when daylight savings time starts and ends. A job scheduling job is used to change the time of day and then changes the job schedule entry for the next date. An option exists to reset QUTCOFFSET.
Set IPL Date. Allows a simple setting of the IPL date and time rather than directly changing the system values. The date value can be entered in the form of *DAY1, *DAY2 etc. A data area is used to provide a changeable default for the time-of-day.
Set Job Log to Print. The SETJOBLOG/FRCJOBLOG commands are intended for those environments where the user has a monitor for CPF0000 and still wants a job log produced at the end of the job if errors have occurred. When the error occurs, the SETJOBLOG command is used to set a data area switch in QTEMP. At the end of the job, the FRCJOBLOG command is used which will cause the job log to occur if the switch was set.
The SETQCMD Attention program provides a simple means for using the full command screen (QCMD) display when the Attention Key is pressed. The SETQUSCMD program is also provided to provide access to the single line command window with the QUSCMDLN program.
Set status message. Provides a simple solution for shutting off status messages from appearing to an end user during the running of certain commands. The same command with a different parameter value resets the current job to the previous setting.
Shout a Message. Provides a method of sending a break message to a list of users. If none of the users are active, a special value *FIRSTUSER may be specified to send a message to the active user on the system that has the highest user type (e.g. *PGMR). Useful for ensuring that critical system conditions are recognized.
The Signoff 2 command operates as a normal signoff command except that ENDCNN(*YES) is the default instead of the system default of *NO. SIGNOFF2 is intended to be used when TELNET is used to start a job on another system. SIGNOFF2 may only be used during an interactive job. The command is specified as LMTUSR(*YES).
The Send Audit Entry command sends a journal entry to the QAUDJRN journal if it exists. If the journal does not exist, a TAA9881 message is sent to QHST. SNDAUDE allows an audit entry to be sent to help identify an audit trail of significant events. An ID (10 characters) must be specified to identify the entry.
The Send Audit Message command provides a simple method of sending a message to your own program message queue. This can be used for auditing or debugging purposes. The SNDAUDM command processing program may also be called from any HLL program.
Send a Break Message to the Active Work Stations. The system supported SNDMSG command can send to all active users, but it cannot force a break message. The system supported SNDBRKMSG function can send a message to all workstations and will cause a break on those that are active. However, the users that are not signed on will see the message when they do signon. OA supports a similar function, but it is not a command.
Send Completion Message. Provides a simple command interface for sending a completion message. The CPP SNDCOMP can be called from any HLL to allow you to easily send a completion message.
Send Diagnostic Message. Provides a simple command interface for sending a diagnostic message. The CPP SNDDIAG can be called from any HLL to allow you to easily send a diagnostic message.
Send Data Queue. Provides a command interface to allow a simple approach for sending and receiving data queue entries. Provides a command interface to the system supplied programs. Both non-keyed and keyed data queues are supported. Useful for low volume functions involving data queues. High volume work should use the system supplied programs directly.
The Send Escape Information command is designed to work in a CL program standard error handling routine such as used in the TAA Productivity Tools. You must first extract the SENDER information from an escape message and specify it on SNDESCINF. SNDESCINF sends a message with the program, library, and MI instruction where the escape message occurred.
Send escape message. Provides a simple command that can be used for sending the CPF9898 escape message with user data as the text. Also allows a simple method of sending an escape message from a HLL program by using a call to SNDESC. A second command SNDESCMSG2 and a second program SNDESC2 allow any message ID to be sent.
The Send Escape Message 3 command allows you to send an escape message with both first level and second level text using an impromptu form of message text. Standard message IDs (TAA9871 - TAA9878) must be used. Two different jobs may use the same ID at the same time and the text will be unique to their individual jobs.
The Send Escape Message 4 command allows you to send an escape message using QCMDEXC or similar functions. The system command SNDPGMMSG or other TAA SNDESCMSGx commands require that the command be in a CL program. SNDESCMSG4 may be used from a Command Exit to cause an escape message.
The Send Escape Message 5 command is similar to the TAA SNDESCMSG2 command (part of the SNDESCMSG tool), but also allows a ‘stack counter’ to be specified. This allows the escape message to be sent to a program higher in the stack than the calling program. The QMHSNDPGM API is used.
The Send Group Profile Members a Message command allows you to send a message to the members of a group profile. Options exist to send only to active users, to send to the signed on message queue, and to send the message as a break message.
The Send Hex Message command sends a message containing hex values (such as X’C1’ or X’03’) and displays the message in both EBCDIC and the converted hex format. This is designed as a testing aid when dealing with hex values.
The Send IFS Mail command sends a note and an IFS attachment to one or more recipients. The recipients are described by using a name and a corresponding E-Mail address that must exist in a MAILADRP file or by entering a specific E-Mail address. The SNDDST command is used internally.
The Send Interactive Jobs a Message command sends a break message to all interactive jobs. Selection by subsystem and generic user can be made. An omit list of users and/or devices can be named (see the Omit list discussion). The command may be used in conjunction with the ENDINTJOB command to inform users a few minutes before ending their jobs.
The Send Job Log Message command provides a simple method of sending a message with a message ID to the job log. This allows for setting a ‘mark’ in the job log that can be read by a tool such as CHKSAVRST. Only the message IDs TAA9871 - TAA9878 may be used.
The Send Long Message command is intended as a debugging aid to send one or more messages from a large variable. This allows the value of the variable to be more easily seen on a command entry display or in the job log. The message length may be between 20 and 512. A ruler is optional.
The Send Message Line command allows a long message to be sent to a joblog or displayed interactively where each line of text from the command is a separate line. Each line of the message can be up to 56 bytes and can be up to 7 lines. SNDMSGLIN avoids a continuous string of text in a message which can be difficult to read.
Send a Message to the Submitter. This command can only be executed in a batch job and provides a simple method of sending a message to the users message queue that submitted the job. Providing a meaningful message when the job aborts can be helpful in eliminating searching thru the job log for the actual error.
Send Network Output Queue. Allows all of the files in a specified output queue to be sent via SNADS. All of the spooled files in the output queue are determined and the SNDNETSPLF command is used on each.
The Send Object Lock Message command sends a break message to workstations that have jobs with locks held on up to 100 different named objects. An option exists to end the jobs after sending a break message. SNDOBJLCKM can be used to inform users that an exclusive function is needed for the objects and ending of the jobs is required. A listing that describes the actions taken is displayed or output.
The Save and Mail Object command simplifies sending objects as an attachment to an Email. The command uses the sub tools SAVOBJIFS and SNDIFSMAIL to create a save file in QTEMP, save the object(s), copy the save file to an IFS stream file, and attach the stream file to an Email which is sent using the SNDDST system command. The TAA Tool RSTOBJIFS may be used to restore the object(s).
The Send Program Information command allows you to send messages about the current program, the calling program, or any specified program to the job log. The command is intended to provide an audit trail in case problems arise. The messages include the create date/time of the program, the source member information and the last change date of the source as found in the program and in the source member (if it exists).
The Send Program Message 2 command allows you to send a message with both first and second level text using an impromptu form of message text. Standard message IDs (TAA9871 - TAA9878) must be used. Two different jobs may use the same ID at the same time and the text will be unique to their individual jobs.
The Send Program Message 3 command allows a *DIAG, *COMP, or *INFO message to be sent to the caller from a sub or sub-sub program. This can provide better feedback when the sub program needs to communicate to the caller of a program. The QMHSNDPM API is used to allow the message to be sent up the stack.
The Send Program Message 4 command is a subset front end to SNDPGMMSG which allows a message ID to be sent from a message file to a message queue. The system SNDPGMMSG command may only be used in a CL program. SNDPGMMSG4 allows any environment and can be helpful when testing either how the message text will appear or to place a message with an ID in a message queue.
The Send Spooled File E-Mail command sends a spooled file in *SCS format with a brief text message to one or more recipients. The recipients are described by using a name and a corresponding E-Mail address that must exist in a MAILADRP file or by entering a specific E-Mail address. The SNDDST command is used internally. See the SNDTXTMAIL command for sending a long text message without a spooled file.
The Send Spooled File as a PDF command sends a normal spooled file as a PDF to one or more users. This allows the end user to view the information with a technique that he may be more familiar with.
The Send Status Count command provides a simple interface for sending a status message describing progress after the processing of n items. This allows the user to be informed of progress by a long running user written function that is processing items such as members or objects. Either a count, a percentage, or a ‘progress bar’ of the completed items may be sent. The command may only be used in a CL program.
Send Status Message. Provides a simple solution for sending or removing a status message from a CL program. The SNDSTS program can also be called directly from a HLL program to send or remove a status message.
The Send TCP Output Queue command sends all spooled files in a named output queue to another system using TCP. The command uses SNDTCPSPLF for each spooled file to be sent.
Send Time Message. Provides a simple solution for sending a message to yourself or another user at a specific date/time. The STRTIMMSG command starts a batch job that listens for entries sent to a data queue by the SNDTIMMSG command. The ENDTIMMSG command ends the batch job. Useful for sending reminder messages to yourself or other users at a specific date/time.
The Send Text E-Mail command sends a text message to one or more recipients. The recipients are described by using a name and a corresponding E-Mail address that must exist in a MAILADRP file or by entering a specific E-Mail address. The SNDDST command is used internally. See the SNDSPLMAIL command for sending an E-Mail with an attached spooled file.
The Send User Group Message command allows you to send a message to all users of a User Group (as defined by the User Group tool). Options exist to send only to active users, to send to the signed on message queue, and to send the message as a break message.
The Send User Break Message command allows a break message to be sent to a user profile name. The workstation where the user is signed onto will receive a break message. The system commands SNDBRKMSG and SNDMSG do not support this function. SNDUSRBRK determines if the user is active and sends the same message to every workstation where the user is signed onto.
The Send Warning Message command is designed for the situation where the user should be informed of a ‘warning’ situation. If the command is run in an interactive job, the text of the message is sent as a diagnostic message.
The Sort CLP DCL command sorts the DCL statements within CL source by variable name or by variable name within DCL type. This allows a consistent approach for how CL source is kept on your system.
The Sort CLP Variable command provides a sort of a number of fixed length elements of up to 100 bytes in a 32,000 byte variable. The data is sequenced in either ascending or descending order and returned in the same variable. The array may be loaded by a tool such as LOOKUP2. The first all blank element or if the variable is full signals the end of the elements.
The Sort Command List command allows the sorting of a simple list. The list would normally be input from a command which allowed multiple entries (such as a list of library names) and you want to process the names in the list in ascending sequence.
Sort Data Base File. Provides a command interface for externally described files to create and/or execute the typical specifications required by the Reformat Utility. Allows simple selection criteria. Useful for front ending batch programs to use arrival sequence processing instead of using keyed processing. Arrival sequence processing is normally much faster if the file to be read is more than 1000-2000 records.
The Sort Data Base File command command provides a front end to OPNQRYF and a sort. The sort is done using an API instead of the OPNQRYF sort. Three significant advantages exist 1) Selection can be specified using a ‘list parameter’ 2) The API sort is faster than the OPNQRYF sort in many cases 3) Since an actual file is created, any utility like function can be used on the sorted data.
The Sort Data Base 2 command provides a command interface for FMTDTA (Reformat Utility command) in support of From/To positions (the SORTDB TAA Tool requires externally described field names). Simple sort field and selection criteria may be specified. Using SORTDB2 can avoid having to know or use the FMTDTA specifications to perform simple sorts.
The Sort RPG Array command sorts compile time array data into ascending sequence for a named array in an RPG type source member. This simplifies making source changes to compile time array data when it is required to be in ascending sequence.
The Sort Source command allows a range of source statements in a source member to be sorted. The output is always to the SORTSRC member of the TAASORTSRC source file in QTEMP. The default is to sort on the entire source data value. From/To positions may be specified. You may then use the SORTSRC member to copy to wherever it is needed.
Sort Text. Sorts the records in a text source member based on a control record entered as the first record and options on the command. Useful for arranging lists for text data.
The Spell command provides a simple name to remember to allow access to the CHKWRD and FNDWRD tools. A menu of all the TAA spell checking tools is also available.
The Spool Archive tool provides a series of commands to convert spooled files into data base file members, track the spooled files, and provide a re-print capability. This provides a complete system for backing up spooled data. No restrictions exist relative to the type of data in the spooled file or the size of the spooled files. A single system can be used to backup spooled files from other systems.
Spool Control. A series of commands that provide two major functions 1) automatic deletion of spooled files after a retention date, 2) backup and retrieving (re-printing) of spooled files. Retrieving allows spooled files to be saved off-line and re-printed at a later date if needed. Backup is done to online save files and then to offline media.
The Spool Distribution tool provides a solution for duplicating spooled files with different attributes and different owners. It allows the specifications of the distribution to be maintained in a data base file external to the program. The DUPSPLDST command accesses the file and duplicates a spooled file with the new parameters.
The Spool Store tool is a series of commands that lets you capture spooled files and retain them online. Two types of Spool Stores are provided 1) an *AUTO type where each spooled file is internally assigned a unique ID, and 2) a *MANUAL type where you assign an ID to each spooled file. Several commands exist to convert, re-print, maintain, and ‘work with’ the Spool Store.
Squeeze Program Size. Can operate on one, generic or all programs in a library to squeeze space. Re-creates CL programs with the option to remove CL source. Allows option to either compress or remove observability. Companion command is DSQPGMSIZ which causes programs to be re-created with observability. Useful for squeezing space.
Source Archive. A series of commands that lets you archive source on-line, ‘copy out’, and display. The source is kept in a compressed format that is typically 25% of the original space. An update command archives any new or changed members found in the source files. A maintenance command cleans up old versions and optionally allows the removal of source members that have not been changed recently.
Source Control. A series of commands that provides for control of source. Uses a ‘check out’ and ‘check in’ concept and provides an archive of any changed source and an audit trail of events. Useful for controlling source and ensuring an orderly change procedure.
Stack of Data in CL Programs. The stack commands (SNDSTK, RCVSTK, UPDSTK, LKPSTK, INZSTK, and SORTSTK) provide a solution for handling a stack of entries in a CL program. The stack is held in a 2000 byte variable within your program. The commands manipulate the stack. This avoids having to code indexing operations within your CL program when a stack of entries is needed.
The Start Batch Debug command assists in debugging a program or service program in batch. STRBCHDBG removes the tedious and confusing steps involved in setting up an environment to debug in batch. With STRBCHDBG, debugging a batch program becomes about as easy as debugging an interactive program. The ILE debugger is used to debug (this will allow debugging of OPM programs).
The Start Journal Library 2 command provides a solution for starting journaling to all or generic named files, data areas, and data queues in a library. The command may also be used to ensure all appropriate objects are journaled in a consistent manner. The companion command End Journal Library 2 ends journaling. An option exists for access path journaling.
Start at Key. This displays a prompt for the key fields of a file. This is primarily a sub-function used by the TAA tool DSPDB.
The Start Object Conversion 2 command is a front end to the system STROBJCVN command. STROBJCVN2 provides an easier solution by allowing a list of named or generic libraries and an omit list of libraries. A listing is produced instead of messages in the job log. Status messages describe which library is being operated on.
The Start Writer command is intended to be used to start either a local or remote output queue. Based on the named output queue, a command prompt appears for either STRPRTWTR or STRRMTWTR.
Sending Work Station Messages as Status Messages. An active work station message queue is normally in either break mode or notify mode. If you normally receive many messages (e.g. batch job has completed), break mode causes an interruption on each message. Notify mode requires that you use DSPMSG. The STSMSG function describes how to turn some or all message IDs into status messages so they can be seen without causing an interruption.
Summarize Journal Entries. The journal entries output from the DSPJRN command are summarized so only a single entry exists for each relative record (RR) number. The companion command APYSUMJRN (Apply Summarized Journal) applies the entries to a file. Useful for avoiding a long recovery time caused by applying many journal entries. The performance is better if many journal entries tend to update the same records.
Swap Library List Entry. Provides a reasonable solution when you want to add a library to the library list and the user may be at the maximum of 25 libraries. The command allows you to swap your library for the last library on the library list. A return variable is provided for the removed library. When your function is complete, you can swap back the removed library.
The Swap Library List Entry 2 command allows a swap of 2 libraries on the user portion of the library list. For example, if both QGPL and QTEMP are in the user portion of the library list and should trade places, the SWPLIBLE2 will make the swap.
The Swap User Profile command allows a swap to a user profile and runs a command under the new user profile. You must have *USE authority to the new user profile, but the authority may be adopted. When the command completes (either normally or abnormally), a special ‘scope’ program is used to ensure a swap back occurs to the original profile. Among other uses, SWPUSRPRF allows a means of adopting when using IFS objects.
The System Activity tool is a series of commands that lets you capture and work with the data produced by the WRKSYSACT system command. This provides performance information for jobs/tasks that have occurred during one or more intervals. The SYSACT tool can be helpful in reviewing performance characteristics such as CPU usage, I/O counts and a breakdown of reads/writes for data base and non-data base activity.
The System History tool provides a simple method of capturing and displaying important system information such as the amount of storage used, amount of CPU used, interactive transactions entered, and the average response time. Capturing the information daily allows you to display or print a historical perspective of system growth.
The System Library List tool is a documentation member only to help understand the basics of how to control and audit the changes to libraries on the system library list. TAA Tools that can assist are also mentioned.
Access Command Entry from the system request display. This describes the technique involving a separate message queue and a break handling program to access command entry from the system request display. This is useful for a variety of functions such as ending debug when editing in SEU. It can also be used for starting debug if an interactive program is looping.
TAA Archive. The TAA source is shipped in an archive in a compressed manner to save storage. Several commands work with the source in the archive. The WRKTAA command provides a listing of the TAA Tools with options to display the heading of the member, display/print the member, or copy out the compressed source to a source file.
The TAA Spell Checking support provides both a rich English language dictionary that includes IBM i and TAA Productivity Tool words along with several commands to check text members and literals within source. If you write in English, it is not necessary to have the system Dictionary product in order to assist you in a variety of spell checking requirements.
The TAAEXC program is intended to be used instead of QCMDEXC from a HLL program to allow for better handling of messages. An externally described data structure is supplied which must be defined in the HLL program. Fields within the data structure allow a command to be passed, options to be set, and information to be returned.
The TAA Query tool provides a simple query method allowing for selection, sequencing, and printing. A data base file holds the specifications which are created from simple prompts. The same query can be used again and/or modified. OPNQRYF is used to perform selection and sequencing which provides performance as fast as any query function on the system. A generalized print approach is used to print the data.
Truncate Spooled File. Provides a solution for the case where you 1) Already have spooled output 2) Need to print on a printer that is not as wide as the print lines 3) Don’t want the ‘fold’ function which produces multiple print lines. TCTSPLF re-prints the spooled file and truncates the print line at a specified position. Useful for dealing with PC printers.
The Time Record tool is a series of commands that allow capturing of time in seconds and 6 digits of sub seconds by using SNDTIMRCD at various points in an application. A journal entry is written. The CVTTIMRCD command may then be used to extract the entries to a data base file.
The Trace Debug tool provides a trace of a program describing the original source statements as they are executed and optionally describing the values of named variables. Both OPM and ILE programs are supported. The source member used for the create must exist. A specific create option is required to provide the debug information in the object.
The Trigger Sample tool provides some sample objects for learning how to write a trigger program. Starting with a sample that uses standard field names for basic trigger fields and your own field names for your data base file makes it simple to write a trigger program. You must copy the code from the TAA Archive to be able to work with it.
The TRIM command is similar to the RPG IV %TRIMx functions. Leading blanks may be trimmed off the left hand side of a value along with specified characters. Trailing characters may also be trimmed off the right side of a value. Because the command returns a 1000 byte variable, there is no concept of trimming off trailing blanks. The length of the returned value may also be returned.
The Trim First Blank command trims an input value after the first blank position. For example, if ‘ABC DEF’ is input, ‘ABC’ is returned. The INPVAL may be up to 256 bytes. The RTNVAL parameter must be specified as *CHAR LEN(256).
Trim Leading Blanks. Provides for trimming off a variable (left adjusting) when there are leading blanks. Useful for functions where the value may not be left adjusted.
The Truncate Deleted Records command is the companion command to CPRDLTRCD. TRNDLTRCD truncates the deleted records starting at the back end of the file to the last active record, resets the ‘end of data’ pointer in the file, and returns space to the system (if it is a large amount).
Translate value. Provides a command interface to the QDCXLATE API for performing a field translation. Useful for folding lower to upper case for a variable or other translation functions in a CL program.
Unadopt. Provides a program which will execute a command in an environment where you do not want adopted authority. A call interface is provided. The program is specified as CHGPGM USEADPAUT(*NO) so that any command that is executed will operate only under the users authority. Useful for executing commands (including CALL) where you want to ensure that only the users authority will be used.
The Unload a Device command provides a simple function to ensure a device is unloaded. If the command completes successfully and unloads the device or the device is not in a ready status (the status if already unloaded), the command completes normally. Different completion message text describes the condition. The command may be helpful when several save commands are used in a CL program and it is not known what the device condition is at the end.
Update field. Allows a simple selection criteria against a single field and updates any selected records with a specified value for a single field. Can also be used to place the same value in all records. Useful in eliminating the need to write simple file maintenance programs to such as changing certain fields or resetting YTD values.
The Update Message File command uses the MSGFP outfile created from the TAA CVTMSGF command to update the message descriptions in a message file. UPDMSGF allows you to keep a data base file of messages or update selected messages on the same or another system.
The Update PFILE in DDS source command causes the PFILE statement in a LF source member to be changed. This can simplify batch create steps involving logical files where different libraries are used. A qualified name is supported.
The Update PFILE 2 command updates one or more LF source type (not LF38) members to change the PFILE keyword to a library qualified value. This allows the source to be changed to indicate that the LF should be built over a PF in a specific library. If the existing physical file is on the library list, attempting to create the new logical file over a copy of the physical can often result in the logical being built over the wrong physical file.
The UPS Monitor tool provides a solution for achieving a normal system power down after a power outage occurs and a delay time has been reached. You must have a UPS attached to the system and understand its capabilities. You must ensure the TAAUPSMON job is running.
The User Groups tool allows you to define a list of users belonging to a group. The support has no connection with the system Group Profile support. Several commands are supported such as Edit, Print, Add, Remove, or Retrieve for User Groups. User Groups may be used for your own application need or by tools such as SNDUSGMSG or GRTUSGAUT.
The User Index tool provides an interface to allow reading, writing, updating, and deleting entries from a user index. Several other tools such as CRTUSRIDX also use interfaces provided by USRIDX. Only keyed fixed length user indexes are supported. The maximum entry length is 2000 bytes including the key.
Validate Data Base File. Accesses any externally described data base file and uses the DDS validity checks specified to validate the data. Finds any invalid numeric data. Non-externally described files are checked for damage. Useful for periodic checking of data base files to ensure integrity or to check for damage. A second command (VALMNYDBF) exists to process all physical members in a library.
The Vary Configuration Off command provides a simple version of the VRYCFG command to vary off a device. The user must be authorized to the TAAVRYCFGO authorization list. The system VRYCFG command requires the user to have *JOBCTL special authority. The intent of VRYCFGOFF is to provide a solution without authorizing a user to *JOBCTL and may be used as an option an option on the SECOFR2 menu.
The Vary Configuration 2 command provides a simple version of the VRYCFG command. The user must be authorized to the TAAVRYCFG authorization list. The system VRYCFG command requires the user to have *JOBCTL special authority. The intent of VRYCFG2 is to provide a solution without authorizing a user to *JOBCTL. VRYCFG2 is used as an option on the SECOFR2 menu.
The Vary Device Off/On command varies a device ‘off’ and then ‘on’ to reset the device. If a Workstation device is named, the Signon display refreshes. This can be useful if ‘Signon Text’ is used such as with the CHGSGNTXT command. An option exists to name a subsystem to allocate the device to a ‘HELD’ status.
The Vary Virtual Display command varies one or more virtual displays off or on, whichever is requested.
Who is Abusing the System. Promotes the user to the highest priority and does WRKACTJOB with selection criteria. After the display appears, press the refresh key (F5) to show who is abusing the system. Useful for quickly determining the user who is causing the system to slow down.
The ‘Who Is’ command provides basic information about a user profile including the last signon date and whether the user has an active job. The information is displayed or listed. You must be authorized to the TAARTVUSR2 authorization list.
The Who Me command provides a simple method for determining the name of the current job, the system name, and the current date/time. Messages are sent describing the information.
Work Activation Groups is a new tool which provides a work display for all activation groups owned by the current job. An option to display attributes is available, as well as a reclaim option to free system resources.
The Work Add Hexadecimal command provides a work display for adding a hex or a decimal value to a hex or decimal value. The hexadecimal values may be entered as either unsigned or signed values. The result is returned as both hex and decimal values. Help text is provided for the display.
The Work All Spooled Files command allows a user designed WRKSPLF display in terms of Options and Function keys. The normal WRKSPLF functions may be chosen along with TAA commands (such as PRTPAGRNG) plus user defined options and function keys. There is no command line by default.
The Work ASP command provides a subfile display with one record per ASP. The major status fields are shown including the total capacity and the amount used. Options are available such as display details, change the attributes, and print the libraries. Special authority is required for some options.
The Work Current User command is similar to the WRKUSRJOB system command except that the current user of the job is also shown. This allows support for jobs that swap profiles to be displayed and operated on. The same options as on WRKUSRJOB such as CHGJOB are supported. Only active jobs are displayed.
The Work Database File Unit tool allows you to inspect and set the preferred storage unit for files on your system.
The Work Disabled User command provides a work display of the users with a *DISABLED status. An option exists to enable the users. An omit list of profiles may be specified which would allow the use of WRKDSAUSR in a CL program where you could omit certain profiles that were known to be disabled.
The Work Fathom command provides an interactive display to convert from fathoms, feet, cable lengths, nautical miles, and miles to different values. By entering a non-zero value on the left of the display and pressing Enter, the screen is refreshed with the converted value.
The Work File 2 command provides a subfile with options to display the attributes, relations, format, and data of a file. These are the same options as on the DSPF2 command. In addition, there are options to change, edit, clear, and delete a file.
The Work IFS command is designed for those users who are trying to cleanup the IFS. Selection criteria exists (such as size or last used date) which can be used to minimize what is displayed in the work display. You may also sequence the display. From the display, the user can display or print attributes and access WRKLNK for any object. *STMF object types may be removed.
The Work IFS 2 command is designed for a review of IFS entries, but does not allow any changes to be made. Several selection and sequencing options exist. The WRKIFS command is similar, but allows removal of entries and access to WRKLNK.
The Work IP Devices command provides a work display of the IP devices and the currently active job (if any). Options exist to 1) Work with the device description, 2) Work with the job, and 3) Work with configuration status. Command parameters allow output to a printer or an outfile.
The Work Job Queue 2 command is similar to the system WRKJOBQ command, but allows all or a generic named job queue in a named or generic library. Similar options exist as with WRKJOBQ to work with, hold, release, etc. If you have multiple job queues in the same library, WRKJOBQ2 can be helpful in reviewing the jobs.
The Work Job Storage command provides a work display or a listing of the temporary storage used by active jobs. Selection criteria exists for the amount of storage, by job, and by user. This provides a simple review of the amount of storage being used. *JOBCTL is required to use WRKJOBSTG.
The Work Job Status command provides a work display or listing of all jobs in one or more named status values such as RUN or DSC. The display has a similar layout and options as the WRKACTJOB display. The jobs appear in job number order as opposed to the subsystem sequence used by WRKACTJOB.
The Work Job 2 command is a more powerful version of the system WRKJOB command. WRKJOB2 supports options for WRKJOB and DSPJOB OUTPUT(*PRINT) and all of the detail options available on the WRKJOB menu. When the option completes, the subfile is re-displayed. WRKJOB2 also allows options for all jobs, all users, job status, and job type.
The Work Journal Library command provides a work display of data base files, data areas, and data queues in a library. Options exist to start and end journaling of objects as well as access path journaling. Options exist on the command to select the objects that should be displayed such as by generic name, the type of object, and whether the objects are journaled not journaled.
The Work Library Auditing command provides a work display for making changes to the create object auditing value for libraries. A named, a generic, or all libraries may be displayed. Selection may be made on the existing library create auditing value.
The Work Members command displays the members of a data base file and provides options to display or change the member level information and the data. The options are similar to the DSPMBRS command with the
The Work Metric command provides a work display that allows conversions of distance, weight, area, and liquid volumes to/from metric values. For example, you can enter a value in meters and see the results in feet and inches or vice versa. Equivalent values are also provided such as how many feet in a Fathom.
The Work Network Attributes command provides a subfile of all network attributes and their current values. A Change option exists to allow a prompt for CHGNETA and the specifically selected network attribute. The existing current value is shown during the prompt. WRKNETA provides a significantly better interface than the system CHGNETA command which prompts for all parameters and shows *SAME.
The Work Object Auditing command provides a work display for making changes to the object auditing value for objects in a library. A named, a generic, or all objects in a library may be displayed. Selection may be made on the existing object auditing value.
The Work Object Text command provides a simple means of reviewing and cleaning up text for objects. A subfile of one or more objects in a library is displayed and allows a direct change to the text. Various selection criteria exist. Options exist to display, change, and delete the objects along with an option to display the object description.
The Work Object 2 command provides more options than the system WRKOBJ command. In addition to the same options as WRKOBJ, WRKOBJ2 supports options for Change/Work, DSPxxx, DSPOBJD2, and MOVOBJ. WRKOBJ2 provides specific commands for options such as CHGJOBD and DSPJOBD if a JOBD object is being displayed. A search pattern is also provided for.
The Work Output Queue 2 command is similar to the system WRKOUTQ command, but allows a list of multiple output queues to be specified and an option for a WRKALLSPLF type program. WRKOUTQ2 does not support a command line such as on WRKOUTQ.
Work Output Queue 3 command is similar to the system WRKOUTQ command, but supports additional capability such as all output queues in a library or all libraries and a ‘Position To’ capability.
The Work Owned Objects command provides a work display for a user profile’s owned objects. The outfile from DSPUSRPRF TYPE(*OBJOWN) is used internally to provide the basic information. Various options exist to work with the objects such as change, delete, display, duplicate, etc.
The Work Remote Output Queue command provides a work display for remote output queues. Options exist such as STRRMTWTR, ENDWTR, HLDWTR, and WRKOUTQ. A print option also exists to provide a listing of all remote output queues. WRKRMTOUTQ lets you focus on the remote output queues.
The Work Roman Numeral tool provides 3 commands. CVTFRMROM converts from a Roman Numeral such as LX to a decimal value. CVTTOROM converts from a decimal value to a Roman Numeral value. WRKROMNUM provides a work display with both functions.
The Work with Save File Members command provides a work display of the members of a saved data base file in a save file. Simple options allow a restore of the member or to display the description of the online member in the file where the member was saved from. WRKSAVFMBR provides a better solution than the system DSPSAVF command. such as the owner of the file has changed, the library doesn’t exist, the file has no members, etc
The Work with Save File Objects command provides a work display of the objects saved in a save file. Simple options allow a restore of the object, access to the WRKSAVFMBR command (for data base files) or to display the object in the library where the object was saved from. WRKSAVFOBJ provides a better solution than the system DSPSAVF command.
The Work Submitted Jobs 2 command is a subset of the system WRKSBMJOB command. WRKSBMJOB2 is designed to be run from a user menu where the end user should be given some, but not all of the options offered by WRKSBMJOB. Command parameters allow selection of the valid end user options.
Work Subsystem Description 2 provides an ‘easier to use’ interface than that provided by the system WRKSBSD command. The initial WRKSBSD2 display describes whether a subsystem is active. If a change is required, each of the sub options (such as Routing Entries) provides a Work display which allows Add, Copy, Change, Remove, and Display functions. When Change or Copy is requested, the current values appear on the command prompt.
The Work Subsystem Job Queues command provides a display of the Job Queues specified for a subsystem and the jobs that are currently on the Job Queues. Options exist to work with the individual jobs (such as Hold, Release, Change) and the Job Queues (such as Hold and Release). WRKSBSJOBQ provides a review of the batch work that is yet to be processed. See DSPSBSJOBQ for a ‘display only’ version.
The Work SMTP Entries command provides a work display of the QATMSMTPA file in QUSRSYS which contains the two part User ID/Address and an E mail address. From the display, you may see the detail of the entry, access WRKDIRE to make a change, or print a listing of the SMTP entries.
The Work Spooled File 2 command is similar to WRKSPLF, but allows better selection criteria. For example, you can select on a generic output queue name, spooled file size, number of pages, and other values. You must have *SPLCTL special authority to specify a user other than *CURRENT.
The Work Spooled File 3 command works in conjunction with the CVTOUTQ or the CPYCVTOUTQ out file. WRKSPLF3 provides a display similar to WRKSPLF of the spooled file records in the outfile. The use of CVTOUTQ/CPYCVTOUTQ provides better selection capability than the system WRKSPLF command. For example, WRKSPLF does not support an OUTQ parameter.
The Work Source command is a subset like WRKMBRPDM function. The intent of the tool is to provide a simple work display for source members on a system that does not have the WRKMBRPDM command or a similar function. This would be typical in some remote or small installations. The TAA EDTSRC command is used to edit the source.
The Work Server Authentication Entries command provides a display of a user, generic user, all users, or all non-Q users for a named server. A *SELECT option exists to provide a display of the existing servers. When a list of users is displayed for a specific server, options exist to add, change, remove, or display authentication entries.
The Work System Value 2 command allows an entry of a string of characters such as ‘LMT’ or ‘LIMIT’ and scans the system value names and text for matches. A work display appears with the matching system values and options to display or ‘work with’. WRKSYSVAL2 simplifies accessing a system value when you know part of the name or a word in the text description.
The Work User Auditing command provides a work display for making changes to user auditing values. A named, a generic, or all user profiles may be displayed. Selection may be made on the object auditing value or the user auditing actions.
The Work User Authorizations command provides a work display for a user profile’s specific authorizations. This excludes the user’s owned objects. The outfile from DSPUSRPRF TYPE(*OBJAUT) is used internally to provide the basic information. Options exist to display the object description, display the authorizations, and edit the authorizations.
The Work Validation Lists command provides a work display for Validation List (*VLDL) objects. From the display, you may create and delete validation lists and access the TAA WRKVLDLE display to work with individual entries for a specific validation list.
The Work Validation List Entries command is a series of commands that simplify working with validation list entries. After creating a Validation List, the remaining functions such as adding, changing, removing, displaying, verifying, retrieving, and converting can be done with TAA commands rather than system APIs.
Write to a Data Base File. Allows writing of a data base file from a CL program. A variable from the program is written to any data base file beginning in position 1. You are responsible for the proper formatting. Useful for unique requirements, but should be used carefully.
The Write IFS tool provides a solution for writing to the IFS from RPG programs using RPG’s SPECIAL file. Sample programs are provided that range from simple to complex in terms of the function that is used. You may use these as models for your programming. A standard program (WRTIFS) exists in TAATOOL that may be called as part of the SPECIAL file.
Write Source. Allows writing or updating of source statements from CL. Special parameters allow a simple generation of fixed form language source like DDS. Allows dynamic creation of source to be followed normally by a create step.
The Z Edit Code RPG Subroutine tool provides two subroutines that can be copied into a program for stripping leading zeros off a field. ZEDITL left adjusts the data. ZEDITR right adjusts the data. The subroutines are helpful when you cannot or prefer not to use the RPG output specs.
The ZIP and UNZIP commands perform standard PC zip and unzip functions for compressing/decompressing data in the IFS. This can be used to provide better performance for the transmission of objects. The Qshell and jar functions are used along with the QTOCVRT API. A DSPZIP command also exists.
The Z Shift RPG Subroutine tool provides two subroutines that can be copied into a program for shifting a character field left or right. ZSHIFTL does a left shift. ZSHIFTR does a right shift. A field length of up to 50 bytes may be processed.