<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="FeedCreator 1.8" -->
<?xml-stylesheet href="https://wiki.parsec.com/lib/exe/css.php?s=feed" type="text/css"?>
<rdf:RDF
    xmlns="http://purl.org/rss/1.0/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
    xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel rdf:about="https://wiki.parsec.com/feed.php">
        <title>PARSEC Technical Information howto</title>
        <description></description>
        <link>https://wiki.parsec.com/</link>
        <image rdf:resource="https://wiki.parsec.com/lib/tpl/dokuwiki/images/favicon.ico" />
       <dc:date>2026-04-26T08:57:11+00:00</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="https://wiki.parsec.com/howto/account_security_-_a_history_and_recommendations?rev=1550090134&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.parsec.com/howto/add_color_to_your_terminal_text?rev=1536618667&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.parsec.com/howto/build_a_vms_chroot_jail?rev=1543868508&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.parsec.com/howto/capture_and_review_vms_boot_startup_scripts?rev=1540323856&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.parsec.com/howto/capture_dcl_command_output_in_a_file_and_on-screen_simultaneously?rev=1536360512&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.parsec.com/howto/clear_your_terminal_screen?rev=1536615509&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.parsec.com/howto/determine_what_your_auto_action_parameter_is_set_to_on_the_alpha_console_from_the_live_system?rev=1550013670&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.parsec.com/howto/find_the_filename_when_all_you_have_is_the_file_id?rev=1549048825&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.parsec.com/howto/fun_with_pipes?rev=1549554752&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.parsec.com/howto/rollover_accounting_datafile?rev=1543867712&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.parsec.com/howto/rollover_operators_logfile?rev=1543867630&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.parsec.com/howto/rollover_security_audit_journal_file?rev=1762295627&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.parsec.com/howto/rollover_system_errlog?rev=1543867666&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.parsec.com/howto/rollover_vms_logfiles?rev=1646260502&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.parsec.com/howto/use_ldann_logical_disks?rev=1736872045&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.parsec.com/howto/what_are_the_various_options_for_backing_up_openvms_data?rev=1653434995&amp;do=diff"/>
            </rdf:Seq>
        </items>
    </channel>
    <image rdf:about="https://wiki.parsec.com/lib/tpl/dokuwiki/images/favicon.ico">
        <title>PARSEC Technical Information</title>
        <link>https://wiki.parsec.com/</link>
        <url>https://wiki.parsec.com/lib/tpl/dokuwiki/images/favicon.ico</url>
    </image>
    <item rdf:about="https://wiki.parsec.com/howto/account_security_-_a_history_and_recommendations?rev=1550090134&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2019-02-13T20:35:34+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>howto:account_security_-_a_history_and_recommendations</title>
        <link>https://wiki.parsec.com/howto/account_security_-_a_history_and_recommendations?rev=1550090134&amp;do=diff</link>
        <description>Introduction

Considered by many to be “that old legacy operating system,” VMS pioneered many security-oriented design approaches, technologies, methodologies, and practices -- its foundations are strong. In many ways, it has earned its reputation as</description>
    </item>
    <item rdf:about="https://wiki.parsec.com/howto/add_color_to_your_terminal_text?rev=1536618667&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2018-09-10T22:31:07+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>howto:add_color_to_your_terminal_text</title>
        <link>https://wiki.parsec.com/howto/add_color_to_your_terminal_text?rev=1536618667&amp;do=diff</link>
        <description>Add Color to Your Terminal Text

The following works for most modern terminal emulators (ANSI-standards-compliant terminals emulated in software, like Putty, Reflection, TeraTerm and others), but will not work on old (antique) VT100/200/etc. terminals.  Those hardware VT-terminals had only single-color phosphors in their cathode-ray tubes (CRTs), like green (hence,</description>
    </item>
    <item rdf:about="https://wiki.parsec.com/howto/build_a_vms_chroot_jail?rev=1543868508&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2018-12-03T20:21:48+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>howto:build_a_vms_chroot_jail</title>
        <link>https://wiki.parsec.com/howto/build_a_vms_chroot_jail?rev=1543868508&amp;do=diff</link>
        <description>How To Build a VMS chroot jail

A VMS sysadmin recently asked us:

	*  “I need a quick and fast way to keep a user only in his/her own directory (SYS$LOGIN), restricting him from changing directory and reading/accessing anything else.  Is there a simple flag I can set in AUTHORIZE (SYSUAF)?  I don’t want to have to change protections on other directories in the system. Reason for this:  We need an external user to be able to login either via</description>
    </item>
    <item rdf:about="https://wiki.parsec.com/howto/capture_and_review_vms_boot_startup_scripts?rev=1540323856&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2018-10-23T19:44:16+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>howto:capture_and_review_vms_boot_startup_scripts</title>
        <link>https://wiki.parsec.com/howto/capture_and_review_vms_boot_startup_scripts?rev=1540323856&amp;do=diff</link>
        <description>How To Capture and Review VMS Boot Startup Scripts

Like that old existential joke about the tree falling in the forest with nobody around to hear it, have you ever wondered what&#039;s happening on your OpenVMS system&#039;s console terminal during a system reboot when you&#039;re not there to look at it?</description>
    </item>
    <item rdf:about="https://wiki.parsec.com/howto/capture_dcl_command_output_in_a_file_and_on-screen_simultaneously?rev=1536360512&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2018-09-07T22:48:32+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>howto:capture_dcl_command_output_in_a_file_and_on-screen_simultaneously</title>
        <link>https://wiki.parsec.com/howto/capture_dcl_command_output_in_a_file_and_on-screen_simultaneously?rev=1536360512&amp;do=diff</link>
        <description>How To Capture DCL Command Output to a Text File and On-Screen Simultaneously

Ever need to both review some DCL command output on-screen and capture it to a file at the same time?

This happens more often than you might guess.  For example, you may need to capture some fast-changing VMS state information (like a process in RWAST state), but doing the same command twice-in-a-row may not show the same overall system state (things can change fast).</description>
    </item>
    <item rdf:about="https://wiki.parsec.com/howto/clear_your_terminal_screen?rev=1536615509&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2018-09-10T21:38:29+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>howto:clear_your_terminal_screen</title>
        <link>https://wiki.parsec.com/howto/clear_your_terminal_screen?rev=1536615509&amp;do=diff</link>
        <description>How To Clear Your Terminal Screen

There you are, happily -- but surreptitiously -- playing away at a vintage game of “Adventure,” when... suddenly, you see the boss approaching!  Quick!  Don&#039;t get caught!  How to erase the evidence of your dalliance?</description>
    </item>
    <item rdf:about="https://wiki.parsec.com/howto/determine_what_your_auto_action_parameter_is_set_to_on_the_alpha_console_from_the_live_system?rev=1550013670&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2019-02-12T23:21:10+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>howto:determine_what_your_auto_action_parameter_is_set_to_on_the_alpha_console_from_the_live_system</title>
        <link>https://wiki.parsec.com/howto/determine_what_your_auto_action_parameter_is_set_to_on_the_alpha_console_from_the_live_system?rev=1550013670&amp;do=diff</link>
        <description>Introduction

There are times when you need to know what the AUTO_ACTION environmental parameter on Alpha is defined.  How would you find out?

Details

First it&#039;s important to understand what the three options are for this parameter:

	*  HALT is clear; whenever the machine gets to the console prompt, it stays there until someone enters a command.</description>
    </item>
    <item rdf:about="https://wiki.parsec.com/howto/find_the_filename_when_all_you_have_is_the_file_id?rev=1549048825&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2019-02-01T19:20:25+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>howto:find_the_filename_when_all_you_have_is_the_file_id</title>
        <link>https://wiki.parsec.com/howto/find_the_filename_when_all_you_have_is_the_file_id?rev=1549048825&amp;do=diff</link>
        <description>Information

There are occasions where you have a File_ID of a file, but not the name.  Probably related to $ ANALYZE/DISK errors such as this one:


%ANALDISK-W-MULTALLOC, file (3224,22,0)
        multiply allocated blocks
        VBN 37225 to 37227
        LBN 6934554 to 6934556, RVN 1</description>
    </item>
    <item rdf:about="https://wiki.parsec.com/howto/fun_with_pipes?rev=1549554752&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2019-02-07T15:52:32+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>howto:fun_with_pipes</title>
        <link>https://wiki.parsec.com/howto/fun_with_pipes?rev=1549554752&amp;do=diff</link>
        <description>How To Have Fun With Pipes

Here are some DCL command aliases that use the PIPE command and construct, just as examples:

Filter through SHOW SYSTEM displays:
$ show symbol ssystem
SSYS*TEM == &quot;PIPE SHOW SYSTEM | SEARCH sys$pipe &quot;
$
$ ssys jones
%SEARCH-I-NOMATCHES, no strings matched    ! user jones is not logged-in, and no batch jobs
$
$ ssys net                                 ! two network processes
2020011E NETACP          HIB     10       48   0 00:00:00.01       162    254
20200140 TCPIP$…</description>
    </item>
    <item rdf:about="https://wiki.parsec.com/howto/rollover_accounting_datafile?rev=1543867712&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2018-12-03T20:08:32+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>howto:rollover_accounting_datafile</title>
        <link>https://wiki.parsec.com/howto/rollover_accounting_datafile?rev=1543867712&amp;do=diff</link>
        <description>How To Rollover Accounting Datafile

1. Locate and check the size of the current ACCOUNTNG.DAT file:


$ SET DEFAULT SYS$MANAGER
$ DIRECTORY /SIZE /DATE /PROTECTION ACCOUNTNG.DAT

Directory SYS$SYSROOT:[SYSMGR]

ACCOUNTNG.DAT;47     1062237  21-JUN-2018 10:53:56.21  (RWED,RWED,RE,)
ACCOUNTNG.DAT;46     1322520   4-FEB-2018 08:38:01.44  (RWED,RWED,RE,)
ACCOUNTNG.DAT;29     3232751  20-SEP-2016 13:25:12.69  (RWED,RWED,RE,)

Total of 3 files, 5617508 blocks.</description>
    </item>
    <item rdf:about="https://wiki.parsec.com/howto/rollover_operators_logfile?rev=1543867630&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2018-12-03T20:07:10+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>howto:rollover_operators_logfile</title>
        <link>https://wiki.parsec.com/howto/rollover_operators_logfile?rev=1543867630&amp;do=diff</link>
        <description>How To Rollover Operator&#039;s Logfile

1. Locate and check the size of the current OPERATOR.LOG file:


$ SET DEFAULT SYS$MANAGER
$ DIRECTORY /SIZE /DATE /PROTECTION OPERATOR.LOG

Directory DSA2:[COMMON]

OPERATOR.LOG;379       51904  17-NOV-2018 08:46:13.29  (RWED,RWED,RE,)
OPERATOR.LOG;378          59  17-NOV-2018 08:16:23.24  (RWED,RWED,RE,)
OPERATOR.LOG;377          45  17-NOV-2018 08:02:09.28  (RWED,RWED,RE,)
OPERATOR.LOG;376          45  17-NOV-2018 07:50:00.22  (RWED,RWED,RE,)
OPERATOR.LOG;3…</description>
    </item>
    <item rdf:about="https://wiki.parsec.com/howto/rollover_security_audit_journal_file?rev=1762295627&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-11-04T22:33:47+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>howto:rollover_security_audit_journal_file</title>
        <link>https://wiki.parsec.com/howto/rollover_security_audit_journal_file?rev=1762295627&amp;do=diff</link>
        <description>How To Rollover Security Audit Journal File

1. Locate and check the size of the current SECURITY.AUDIT$JOURNAL file:


$ SET DEFAULT SYS$MANAGER
$ DIRECTORY /SIZE /DATE /PROTECTION SECURITY.AUDIT$JOURNAL

Directory SYS$COMMON:[SYSMGR]

SECURITY.AUDIT$JOURNAL;18
                      271030   1-AUG-2018 10:03:56.14  (RWED,RWED,RE,)
SECURITY.AUDIT$JOURNAL;17
                      636538   4-FEB-2018 08:37:07.26  (RWED,RWED,RE,)

Total of 2 files, 907568 blocks.</description>
    </item>
    <item rdf:about="https://wiki.parsec.com/howto/rollover_system_errlog?rev=1543867666&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2018-12-03T20:07:46+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>howto:rollover_system_errlog</title>
        <link>https://wiki.parsec.com/howto/rollover_system_errlog?rev=1543867666&amp;do=diff</link>
        <description>How To Rollover System ErrLog

1. Locate and check the size of the current ERRLOG.SYS file:


$ SET DEFAULT SYS$ERRORLOG
$ DIRECTORY /SIZE /DATE /PROTECTION ERRLOG*.*

Directory SYS$SYSROOT:[SYSERR]

ERRLOG.OLD;15           4374  22-DEC-2017 11:26:05.97  (RWED,RWED,RE,)
ERRLOG.OLD;14             97   8-DEC-2017 11:26:04.89  (RWED,RWED,RE,)
ERRLOG.OLD;13            219  17-MAY-2010 16:42:34.30  (RWED,RWED,RE,)
ERRLOG.SYS;1             282   9-NOV-2018 09:50:42.14  (RWED,RWED,RE,)

Total of 4 file…</description>
    </item>
    <item rdf:about="https://wiki.parsec.com/howto/rollover_vms_logfiles?rev=1646260502&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2022-03-02T22:35:02+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>howto:rollover_vms_logfiles</title>
        <link>https://wiki.parsec.com/howto/rollover_vms_logfiles?rev=1646260502&amp;do=diff</link>
        <description>How To Rollover VMS Logfiles

There are four major VMS logfiles that should be rolled-over, or refreshed, on a periodic basis, from both a disk space management perspective and from an ease of use (for the system administrator) perspective.  These files are (shown in their</description>
    </item>
    <item rdf:about="https://wiki.parsec.com/howto/use_ldann_logical_disks?rev=1736872045&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-01-14T16:27:25+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>howto:use_ldann_logical_disks</title>
        <link>https://wiki.parsec.com/howto/use_ldann_logical_disks?rev=1736872045&amp;do=diff</link>
        <description>How To Use LDAnnn: Logical Disks

Logical Disks, presented in OpenVMS as LDAnnn: devices, are one of the operating system&#039;s best-kept secrets, even though there&#039;s really no conspiracy.  Implemented as a Files-11 file system inside of a “container file,</description>
    </item>
    <item rdf:about="https://wiki.parsec.com/howto/what_are_the_various_options_for_backing_up_openvms_data?rev=1653434995&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2022-05-24T23:29:55+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>howto:what_are_the_various_options_for_backing_up_openvms_data</title>
        <link>https://wiki.parsec.com/howto/what_are_the_various_options_for_backing_up_openvms_data?rev=1653434995&amp;do=diff</link>
        <description>NOTE: This is a work in progress. Please forgive the incompleteness until it&#039;s final result. If you have ideas or comments, please send us email and we&#039;ll be happy to review them.

INTRODUCTION

There are a wide variety of ways to back data up on an OpenVMS system. This wiki page will provide the basic concepts of how each mechanism works and provide pointers to more detailed information on how to perform each of these techniques yourself.</description>
    </item>
</rdf:RDF>
