Opel Diagnostics - OPCOM V1.45 Setup & Installation: IntroductionThis Instructable will help you set up and use the Opel hardware and software. It is specific to OPCOM V1.45 which was made in China. It was developed a number of years ago and software support has diminished since then. It is for this r. On this page, you can generate Activation Code for your OP-COM program. This is needed after an installation, or re-installation, and sometimes after installing an update. Please fill out the three textbox below, and then click on the 'Send E-Mail' button. Please copy your computer ID into the following textbox. Please enter your name to the.

The customize operation (-C flag) can be executed at this time. The running system's operating system must be a version greater than or equal to the operating system version of the volume group that undergoes the 'wake-up.' This might mean that it is necessary to boot from the altinst_rootvg and 'wake up' the old_rootvg. Op-com Help Needed - posted in VX220 Discussion: I have just bought a Op-com off flee bay trouble is i can't get it to work keeps asking for activation code which i cant find i tried registering it but it says chines illegal copy i have emailed the seller but know reply just wondered if anyone has any ideas. I tested it also and it can program Underhood electrical center UEC which 090820d couldn't work, i used it on vectra C for daytime running lights adjustment (mode 3) Hvala VZ. I've read the 'opcom activation.pdf' and i didn't find the 'activate password.exe' file from the second point. Where i can find it?

-->

This article describes the password policies and complexity requirements associated with user accounts in your Azure Active Directory (Azure AD) tenant.

Administrator reset policy differences

Opcom is a tool that use opcom software. The last opcom version is 150406 EN and 150506 DE. Both is ask to upgrade the firmware in tge opcom tool to fw 1.64 So for opcom clones: - if you are using opcom china clone 08-2010 which is actually opcom 100219a then the tool must have fw1.39 ( no newer ).

Microsoft enforces a strong default two-gate password reset policy for any Azure administrator role this policy may be different from the one you have defined for your users and cannot be changed. You should always test password reset functionality as a user without any Azure administrator roles assigned.

With a two-gate policy, administrators don't have the ability to use security questions.

The two-gate policy requires two pieces of authentication data, such as an email address, authenticator app, or a phone number. A two-gate policy applies in the following circumstances:

• All the following Azure administrator roles are affected:

  • Helpdesk administrator
  • Service support administrator
  • Billing administrator
  • Partner Tier1 Support
  • Partner Tier2 Support
  • Exchange administrator
  • Skype for Business administrator
  • User administrator
  • Directory writers
  • Global administrator or company administrator
  • SharePoint administrator
  • Compliance administrator
  • Application administrator
  • Security administrator
  • Privileged role administrator
  • Intune administrator
  • Application proxy service administrator
  • Dynamics 365 administrator
  • Power BI service administrator
  • Authentication administrator
  • Privileged Authentication administrator

• If 30 days have elapsed in a trial subscription; or

• A vanity domain is present, such as contoso.com; or

• Azure AD Connect is synchronizing identities from your on-premises directory

Exceptions

A one-gate policy requires one piece of authentication data, such as an email address or phone number. A one-gate policy applies in the following circumstances:

• It's within the first 30 days of a trial subscription; or
• A vanity domain isn't present (*.onmicrosoft.com); and
• Azure AD Connect isn't synchronizing identities

UserPrincipalName policies that apply to all user accounts

Every user account that needs to sign in to Azure AD must have a unique user principal name (UPN) attribute value associated with their account. The following table outlines the policies that apply to both on-premises Active Directory user accounts that are synchronized to the cloud and to cloud-only user accounts:

Property	UserPrincipalName requirements
Characters allowed	A – Z a - z 0 – 9 ' . - _ ! # ^ ~
Characters not allowed	Any '@' character that's not separating the username from the domain. Can't contain a period character '.' immediately preceding the '@' symbol
Length constraints	The total length must not exceed 113 characters There can be up to 64 characters before the '@' symbol There can be up to 48 characters after the '@' symbol

Password policies that only apply to cloud user accounts

The following table describes the password policy settings applied to user accounts that are created and managed in Azure AD:

Property	Requirements
Characters allowed	A – Z a - z 0 – 9 @ # $ % ^ & * - _ ! + = [ ] { } : ‘ , . ? / ` ~ ' ( ) ; blank space
Characters not allowed	Unicode characters. Cannot contain a dot character '.' immediately preceding the '@' symbol”.
Password restrictions	A minimum of 8 characters and a maximum of 256 characters. Requires three out of four of the following: Lowercase characters. Uppercase characters. Numbers (0-9). Symbols (see the previous password restrictions).
Password expiry duration	Default value: 90 days. The value is configurable by using the Set-MsolPasswordPolicy cmdlet from the Azure Active Directory Module for Windows PowerShell.
Password expiry notification	Default value: 14 days (before password expires). The value is configurable by using the Set-MsolPasswordPolicy cmdlet.
Password expiry	Default value: false days (indicates that password expiry is enabled). The value can be configured for individual user accounts by using the Set-MsolUser cmdlet.
Password change history	The last password can't be used again when the user changes a password.
Password reset history	The last password can be used again when the user resets a forgotten password.
Account lockout	After 10 unsuccessful sign-in attempts with the wrong password, the user is locked out for one minute. Further incorrect sign-in attempts lock out the user for increasing durations of time. Smart lockout tracks the last three bad password hashes to avoid incrementing the lockout counter for the same password. If someone enters the same bad password multiple times, this behavior will not cause the account to lockout.

Set password expiration policies in Azure AD

A global administrator or user administrator for a Microsoft cloud service can use the Microsoft Azure AD Module for Windows PowerShell to set user passwords not to expire. You can also use Windows PowerShell cmdlets to remove the never-expires configuration or to see which user passwords are set to never expire.

This guidance applies to other providers, such as Intune and Office 365, which also rely on Azure AD for identity and directory services. Password expiration is the only part of the policy that can be changed.

Note

Only passwords for user accounts that are not synchronized through directory synchronization can be configured to not expire. For more information about directory synchronization, see Connect AD with Azure AD.

Set or check the password policies by using PowerShell

To get started, you need to download and install the Azure AD PowerShell module. After you have it installed, you can use the following steps to configure each field.

Check the expiration policy for a password

1. Connect to Windows PowerShell by using your user administrator or company administrator credentials.

2. Execute one of the following commands:

   • To see if a single user’s password is set to never expire, run the following cmdlet by using the UPN (for example, aprilr@contoso.onmicrosoft.com) or the user ID of the user you want to check:
   • To see the Password never expires setting for all users, run the following cmdlet:

Set a password to expire

1. Connect to Windows PowerShell by using your user administrator or company administrator credentials.

2. Execute one of the following commands:

   • To set the password of one user so that the password expires, run the following cmdlet by using the UPN or the user ID of the user:
   • To set the passwords of all users in the organization so that they expire, use the following cmdlet:

Set a password to never expire

1. Connect to Windows PowerShell by using your user administrator or company administrator credentials.

2. Execute one of the following commands:

   • To set the password of one user to never expire, run the following cmdlet by using the UPN or the user ID of the user:
   • To set the passwords of all the users in an organization to never expire, run the following cmdlet:

   Warning

   Passwords set to -PasswordPolicies DisablePasswordExpiration still age based on the pwdLastSet attribute. If you set the user passwords to never expire and then 90+ days go by, the passwords expire. Based on the pwdLastSet attribute, if you change the expiration to -PasswordPolicies None, all passwords that have a pwdLastSet older than 90 days require the user to change them the next time they sign in. This change can affect a large number of users.

Next steps

The following articles provide additional information about password reset through Azure AD:

• Reset or change your password.
• Register for self-service password reset.

Join GitHub today

GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.

Sign up

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Comments

Environment data VS Code version: 1.27.1 (user setup) Extension version (available under the Extensions sidebar): 2018.8.0 OS and version: Windows 10 Python version (& distribution if applicable, e.g. Anaconda): Python 3.7.0 Type of virtual environment used (N/A venv virtualenv conda ..): venv Relevant/affected Python packages and their versions: N/A Actual behavior Create python terminal results in a powershell error Expected behavior I don't need need to disable running scripts in able to use VS code Steps to reproduce: Fresh install of windows install python create virtual environment try to activate it in VS Code

Hmmm. this feels like it might be a VSCode problem. To fix the issue, you can simply open a Powershell window as administrator and type the following: And hit enter, respond y to any prompts that appear.

I take it back - we are running an activate.ps1 file from a .venv! Hmmm.. not sure what we can do about this from the extension's perspective. @DonJayamanne can we inject some powershell code prior to running activate.ps1 when we launch a python terminal?

can we inject some powershell code prior to running activate.ps1 when we launch a python terminal? Yes we can. Changing the label, as this isn't a bug. we're trying to improve the UX for users of the extension. @d3r3kk Your original suggestion works, changing the policy will work, however @qubitron doesn't want to have to do it manually. Basically we should do what ever we can to remove/reduce such road blocks.

Yep, that's pretty standard Powershell behaviour/expected workflow on a new machine. Not sure we should usurp that is what I'm getting at. However, if we choose to do so, it shouldn't be too difficult to put a quick popup and ask the user if doing so will be ok with them first (much like the powershell cmdlet Set-ExecutionPolicy does).

However, if we choose to do so, it shouldn't be too difficult to put a quick popup and ask the user if Agreed. After all, we're executing some script that we have no control over. @qubitron thoughts

This will require elevation to set the execution policy correct? Not all users have admin rights on the system What if the user doesn't want this execution policy set for security reasons, it's off by default for a reason? Why do we even need powershell cmdlet to do this, why can't we run a batch file or something else that doesn't require admin privileges/execution policies to be set?

It's a PowerShell script because that's how you get the prompt updated to list the virtual environment's name: https://github.com/python/cpython/blob/master/Lib/venv/scripts/nt/Activate.ps1

The other option any notification could have is offer to switch off the automatic activation on top of providing instructions on how to change the policy.

OK, so really this is an issue because we're using a powershell cmd prompt instead of CMD (which is what I use outside of VS Code and just lets me activate without having to set any policies). Since I assume we can't change the default from powershell to cmd, detecting the issue and prompting users to set the execution policy (with a button) seems like the right solution.

commented Sep 13, 2018•

Well, we could do the following: If shell is powershell If batch file exists, then shell into CMD and execute bath file Else if, powershell script exists, excute powershell script, with the prompts to elevate if necessary. I.e. where possible use batch files. This would be better as we wouldn't have to display prompts for powershell script exec elevation..

It might also be easier for us to contribute upstream to Python an Activate.ps1 that isn't automatically generated and thus can be signed as necessary.

Opcom Activate Password Execution Date

Just to add to the description of the issue at hand I had same problem using Pipenv virtual environment. Pipenv version: 2018.11.14 VSCode version : 1.29.1 Worked after updating my execution policy from using the following PS cmdlet: Here is the link to the documentation on ExecutionPolicy from Microsoft Cheers

Not sure if this happens after the latest update but when I execute 'Run current file in terminal', it tries to activate the environment that resides in the same directory with the script itself, it fails and afterwards it executes the script with the python interpreter that is inside my environment. How come ?

@BurakcanK Is the problem due to Powershell permissions not being set? If so, please run (as admin on your system) the Set-ExecutionPolicy as defined above if that is satisfactory for you and your IT department. If that is not the problem you are seeing, please feel free to open another issue with the specific details of your situation.

I was able to work around this problem by adding the following to my VS Code settings:

OPEN POWERSHELL IN ADMINISTRATER MODE AND USE THIS COMMANDS REFERENCE : https://docs.microsoft.com/da-dk/powershell/module/microsoft.powershell.core/about/about_execution_policies?view=powershell-5.1 I hope your problem is solved if not then just follow the reference link

If https://bugs.python.org/issue37354 can be solved then Activate.ps1 can be signed and thus acceptable in a stricter execution policy.

OPEN POWERSHELL IN ADMINISTRATER MODE AND USE THIS COMMANDS REFERENCE : https://docs.microsoft.com/da-dk/powershell/module/microsoft.powershell.core/about/about_execution_policies?view=powershell-5.1 I hope your problem is solved if not then just follow the reference link This Work on my windows 10

Watch python/cpython#14967, may even make it into 3.8.

@d3r3kk it won't make it into 3.8.

@luabud@brettcannon we should evaluate other solutions since this won't be fixed within the next 1-2 years on the Python side then. At a minimum, let's make sure to include this step in our getting started docs.

@qubitron docs are probably going to be all we can do for this as I'm not comfortable overwriting someone's Activate.ps1 on their behalf nor do I want us to have to maintain a custom one. So I think a doc change is probably our best option.

Opcom Activate Password Execution Tool

commented Aug 9, 2019•

edited

@qubitron@brettcannon Agreed on the docs part, but what about prompting to change the execution policy for PowerShell in VS Code, and if 'yes' is selected then we add 'terminal.integrated.shellArgs.windows': ['-ExecutionPolicy', 'Bypass'] to settings.json?

@luabud we could, but I'm a little hesitant since it's a security change so we would have to be very careful and clear on the messaging of what they are opting into having us do on their behalf.

@qubitron@brettcannon looks like we already have that on our Getting Started tutorial: https://code.visualstudio.com/docs/python/python-tutorial#_install-and-use-packages

It's pretty buried in there, I think it should be higher up as a pre-requisite, and the doc it links to lists a ton of options, when it could be more prescriptive and say: Open an administrator powershell prompt (windows key -> type 'Powershell' -> Ctrl+Shift+Enter), and then type:

@d3r3kk it won't make it into 3.8. I think maybe?

Bit shocked Steve's taking that as a bugfix, but 🤷‍♂ .

commented Aug 13, 2019•

edited

Not sure whether we've explored this. Here's what I tried and it works, basically bypass the restriction temporarily, then restore it (applies only to current session): Set-ExecutionPolicy -ExecutionPolicy Unrestricted -Scope Process ; & ./venv/scripts/activate.ps1 ; Set-ExecutionPolicy -ExecutionPolicy Default -Scope Process 3 commands chained First disable for current process (only current process) Next perform activation (based on docs, if a prompt is necessary, it will be displayed to the user - great) Finally, after env activation, we restore the execution policy Pros: We can optionally add a prompt (yes/no) using the -Confirm flag, giving the user more control. Set-ExecutionPolicy -Confirm -ExecutionPolicy Unrestricted -Scope Process ; & ./venv/scripts/activate.ps1 ; Set-ExecutionPolicy -ExecutionPolicy Default -Scope Process It works (unless there's something wrong I can't see) We bypass security only for execution of the activation scripts Changes to policies are scoped to the current process and safely restored (we could make this a script if required) Using the policy of Unrestriced will result in a prompt being displayed to user for downloaded scripts - i.e. letting user decide - I think thats a good thing). We can determine the current execution level as well (VS Code have recently added the ability to create terminals that aren't visible to users. This way we can create a terminal and run scripts to determine the execution level - if we want to do so) Finally: I tried and works on a vanilla Windows 10 setup (had to install one today to test something else). Execution policy is Restricted before and after the above scripts are executed User is prompted (Yes/No) when using the -Confirm flag Works as expected

commented Aug 13, 2019•

Unless no one has any objections, I'd like to revisit this, at least as a spike.

Activate.ps1 will be signed starting in Python 3.8, so I don't know if we want to go down the route of trying to hack around this if it will be solved implicitly over time and won't have us trying to do more in the terminal which we know from experience is extremely finicky.

Previous | Contents

The following example sets the default device and directory to DMA1:[SMITH.COM]:

2.3.7 Setting DCL Verification

Use the SET PROFILE/VERIFY command to turn on DCL verification, which displays DCL command lines and data lines as they execute.

SYSMAN can execute DCL commands using the DO command. By default, SYSMAN DCL verification is turned off.

Example

2.3.8 Executing DCL Commands from SYSMAN

The SYSMAN command DO executes DCL command procedures and SYSMAN command procedures on all nodes in an OpenVMS Cluster environment. In an OpenVMS Cluster environment or in any environment with multiple nodes, you enter a set of commands once, and SYSMAN executes the commands sequentially on every node in the environment. SYSMAN displays the name of each node as it executes commands, or an error message if the command fails.

If a node does not respond within a given timeout period, SYSMAN displays a message before proceeding to the next node in the environment. You can specify a timeout period with the SET TIMEOUT command.

Each DO command executes as an independent subprocess, so no process context is retained between DO commands. For this reason, you must express all DCL commands in a single command string, and you cannot run a procedure that requires input.

In an OpenVMS Cluster environment, SYSMAN executes DO commands sequentially on all nodes in the cluster. After a command completes or times out on one node, SYSMAN sends it to the next node in the environment. Any node that is unable to execute a command returns an error message.

For more information about using the DO command to manage an OpenVMS Cluster system, see Section 20.6. You can also refer to the OpenVMS System Management Utilities Reference Manual for a complete description of the SYSMAN command DO.

Example

In the following example, SYSMAN runs the INSTALL utility and makes a file known on all nodes in the cluster when you enter the commands from the local node:

2.3.9 Creating SYSMAN Command Procedures

The SYSMAN execute procedure (@) command executes SYSMAN command procedures on each node in the environment.

Example

The following example creates and executes a SYSMAN command procedure to display the current date and system time for each OpenVMS Cluster node:

2.3.10 Setting Up SYSMAN with an Initialization File

You can create an initialization file that is used each time you invoke SYSMAN. In the initialization file, you can perform tasks such as defining keys and setting up your environment.

The default file specification for the SYSMAN initialization file is SYS$LOGIN:SYSMANINI.INI. If you want your SYSMAN initialization file to have a different file specification, you must define the logical name SYSMANINI to point to the location of the file.The following is a sample initialization file that defines several keys:

The operator communication manager (OPCOM) is a tool for communicating with users and operators on the system. OPCOM allows you to perform the following functions:Function

For More Information
To broadcast messages to users who are logged in	Section 2.4.3
To control the use of OPA0: as an operator terminal	Section 2.4.4
To designate terminals as operator terminals, enabling them to display messages broadcast by OPCOM	Section 2.4.5
To record messages broadcast by OPCOM in a log file	Section 18.6.3
To send requests to an operator¹	Section 2.4.6
To reply to operator requests¹	Section 2.4.7

¹These functions are used in sites where operators are assigned to help users mount disk or tape volumes and printer forms.

2.4.1 Understanding OPCOM

Opcom Activate Password Execution Button

Figure 2-3 illustrates the function of OPCOM.

Figure 2-3 Operator Communication Manager (OPCOM)

OPCOM Components

OPCOM uses the following components:Component

Description	For More Information
OPCOM process	The system process that manages OPCOM operations. Unless you disable it, the OPCOM process starts automatically at system startup time.	Section 2.4.2
Operator terminals	Terminals designated to display messages broadcast by OPCOM. Usually, the console terminal (with the device name OPA0:) is the operator terminal. However, you can designate any user terminal as an operator terminal.	Section 2.4.5
Operator log file	A file that records messages broadcast by OPCOM. The file is named SYS$MANAGER:OPERATOR.LOG.	Section 18.6.1
OPCOM messages	Messages broadcast by OPCOM. These messages are displayed on operator terminals and written to the operator log file. The messages might be general messages sent by you, user requests, operator replies, or system events.	Section 18.6.2
REPLY and REQUEST commands	DCL commands that allow you to use and control OPCOM.	Section 2.4.3, Section 2.4.6, and Section 2.4.7

OPCOM Defaults

OPCOM uses the following defaults:

• OPCOM is started by default on all systems.
• Except for workstations in an OpenVMS Cluster environment, OPCOM logs messages to OPA0:, which is enabled by default as an operator terminal. The log file SYS$MANAGER:OPERATOR.LOG is opened, and all OPCOM classes are enabled on both the operator terminal and the log file.
  Section 2.4.4 explains how to control the use of OPA0: as an operator terminal. Section 18.6.3.2 explains how to specify the default state of operator log files.

OPCOM Requirements

OPCOM has the following requirements:

• To execute a REPLY command, OPCOM must be running, and you must enter REPLY from a terminal device designated as an operator terminal.
• The REPLY command requires at least OPER privilege. You must have SHARE privilege if another process is logged in to the designated operator terminal. To enable or disable the security class, you must have SECURITY privilege.
• To designate an operator terminal in batch or SYSTARTUP, you must assign SYS$COMMAND to a valid terminal device.

2.4.2 Starting OPCOM

The OPCOM process starts automatically during system startup, unless it is disabled. You might need to start OPCOM interactively if a software problem causes the process to fail and prevents OPCOM from restarting automatically.

To start OPCOM, enter the following command from the system manager's account (SYSTEM):

If a software problem causes OPCOM to fail, contact your Digital support representative. Be sure to keep the process dump file named SYS$SYSTEM:OPCOM.DMP. (When OPCOM fails, it creates this file.)

2.4.3 Sending Messages to Users

To broadcast a message to users, enter the DCL command REPLY as follows:

For example:

Use the following qualifiers to control OPCOM messages:Qualifier

Description
/ALL	Broadcasts a message to all terminals that are attached to the system or cluster. These terminals must be turned on and have broadcast-message reception enabled.
/BELL	Rings a bell at the terminal receiving a message when entered with the /ALL, /TERMINAL, or /USERNAME qualifier; two bells when entered with the /URGENT qualifier; and three bells when entered with the /SHUTDOWN qualifier.
/NODE[=( node-name[,...])	Broadcasts a message to the local cluster node only, or to a node or nodes you specify.
/SHUTDOWN	Sends a message beginning 'SHUTDOWN...'; if used with the /BELL qualifier, rings three bells at terminals receiving the message.
/TERMINAL=( terminal-name[,..])	Broadcasts the message to the specified terminals.
/URGENT	Broadcasts a message beginning 'URGENT...'; if used with the /BELL qualifier, rings two bells at terminals receiving the message.
/USERNAME=( username[,...])	Broadcasts a message to all terminals at which users are logged in to the system (or cluster), or only to the terminals of the specified users.

For more information, see the OpenVMS DCL Dictionary.

Examples

The REPLY command in the following example sends a message to all users logged in to node WLDWND. When the message is displayed, a bell rings at the terminal.

The REPLY command in the following example sends a message to the user logged in at terminal TTC1. When the message is displayed, a bell rings at that terminal.

2.4.4 Controlling the Use of OPA0: as an Operator Terminal

You can control the use of OPA0: as an operator terminal, whether or not the node is part of an OpenVMS Cluster system, by defining the following logicals in SYS$MANAGER:SYLOGICALS.COM:Logical Name

Function
OPC$OPA0_ENABLE	Defined as True or False; if True, specifies that OPA0: is to be enabled as an operator terminal.
OPC$OPA0_CLASSES	Specifies the operator classes that are enabled for OPA0. The logical name can be a search list of the allowed classes, a comma-separated list, or a combination of the two.

The logicals take effect the next time you boot the system.

2.4.5 Designating Operator Terminals

Normally, the console terminal (with the device name OPA0:) is automatically an operator terminal except for workstations in an OpenVMS Cluster environment. However, you can designate any terminal as an operator terminal. You can also disable a previously designated operator terminal.

Enabling Operator Terminals

To designate a terminal as an operator terminal, enter the REPLY/ENABLE command at the terminal. For example:

To designate an operator's terminal in batch or in startup command procedures, SYS$COMMAND must be assigned to a valid terminal device.

If your facility is large, there may be several operators, each of whom is assigned to specific tasks. If this is the case, you can specify the classes of messages the operator terminal receives and responds to when you enable the operator terminal, as follows:

The following table describes each keyword:Keyword

Description
CARDS	Displays messages sent to the card readers.
CENTRAL	Displays messages sent to the central system operator.
CLUSTER	Displays messages from the connection manager pertaining to OpenVMS Cluster system state changes.
DEVICES	Displays messages pertaining to mounting disks.
DISKS	Displays messages pertaining to mounting and dismounting disk volumes.
LICENSE	Displays messages pertaining to software licenses.
NETWORK	Displays messages pertaining to networks; the keyword CENTRAL must also be specified to inhibit network messages.
OPER1 to OPER12	Displays messages sent to operators identified as OPER1 to OPER12.
PRINTER	Displays messages pertaining to print requests.
SECURITY	Allows messages pertaining to security events; requires SECURITY privilege.
TAPES	Allows messages pertaining to mounting and dismounting tape volumes.

For example:

Disabling Operator Terminals

A terminal that you designate as an operator's terminal remains enabled even when the operator logs out. To return the terminal to normal (nonoperator) status, enter the REPLY/DISABLE command from the terminal.

Example

The following example designates terminal TTA3 as an operator terminal, enabling it to receive messages concerning printers, magnetic tapes and disks, and messages intended for the central operator. Later, it relinquishes terminal TTA3's ability to receive messages concerning tapes. The terminal still receives and can respond to messages about disks and printers and messages directed to CENTRAL.

2.4.6 Sending Requests to an Operator

In sites where operators are assigned to assist users by mounting volumes and changing printer forms, users can communicate with operators by entering the DCL command REQUEST and the following qualifiers:Qualifier

Description
/REPLY	Sends a request and requests a reply to the message. Requests sent with this command are issued a unique identification number to which the operator sends the response. The user cannot enter any commands until the operator responds.
/TO=( operator[,...])	If your facility is large, there may be several operators, each of whom has specific tasks. The /TO qualifier lets users send requests to a specific operator. Options are as follows: CARDS, CENTRAL, CLUSTER, DEVICES, DISKS, NETWORK, OPER1 to OPER12, PRINTER, SECURITY, TAPES.

The DCL commands MOUNT/ASSIST and BACKUP/ASSIST also request operator assistance. For more information, see the following sections:

• For MOUNT requests, see Section 8.5.3.
• For BACKUP requests, see Section 10.9.1.

Example

An operator is monitoring an operator terminal enabled for the PRINTER class. The following PRINT command submits an output job that requires a special print form (/FORM=LETTER). The REQUEST command sends a message to the operator. After completing the request, the operator would send a reply, as explained in Section 2.4.7.

2.4.7 Replying to Operator Requests

In sites where operators are assigned to assist users by mounting volumes and changing printer stock, operators can reply to user requests using the DCL command REPLY and the following qualifiers:Qualifier

Description
/ABORT= identification-number	Replies to the request specified by the identification number and cancels the request.
/PENDING= identification-number	Replies to the request specified by the identification number and prevents the user from entering other commands until the operator fulfills or aborts the request. The current terminal must be enabled as an operator terminal.
/STATUS	Reports which classes are enabled, and all outstanding user requests for the terminal from which this command was entered. The current terminal must be enabled as an operator terminal.
/TO= identification-number	Replies to the request specified by the identification number and completes the request. The current terminal must be enabled as an operator terminal. Note that you can also use a variation of the REPLY/TO command in response to a MOUNT/ASSIST and BACKUP/ASSIST commands. For more information, see Section 8.5.3 and Section 10.9.1.

An operator working with magnetic tapes would also use additional REPLY qualifiers specific to magnetic tape operations. For more information, see Section 8.8.2.4. For detailed information on the REPLY command and its qualifiers, see the OpenVMS DCL Dictionary.

Example

In the following example, the REPLY/TO command replies to operator request number 5, issued by user ROBINSON. The MOUNT device is switched to DUA4, and the user is notified.

On VAX systems, the command procedure SYS$UPDATE:VMSKITBLD.COM allows you to duplicate system files from an existing system disk on another disk.

On Alpha systems, procedures similar to those in the VMSKITBLD.COM procedure are performed by the AXPVMS$PCSI_INSTALL.COM procedure. See Section 3.1.2 and also the OpenVMS Alpha Version 7.1 Upgrade and Installation Manual.

The SYS$UPDATE:VMSKITBLD.COM procedure offers the following options:Option

Description	For More Information
BUILD	Builds a new common system disk after destroying all existing files on the disk.	Section 2.5.1
COPY	Copies the operating system files to an existing disk without destroying nonsystem files that are currently on the disk.	Section 2.5.2
ADD	Adds a new system root directory to an existing system disk.	Section 2.5.3

VMSKITBLD uses two disks:Disk

Description
Source disk	The disk from which you copy system files. The source disk must be an existing system disk.
Target disk	The disk to which you move the system files.

Caution

Do not attempt to use VMSKITBLD with the current system disk as the target disk. VMSKITBLD.COM deletes files that are required for a running system.

2.5.1 Using VMSKITBLD.COM to Build a New System Disk

At some point, you might want to create a new system disk. For example, suppose that your existing system disk is an RA81 disk. If you purchase a larger RA90 disk and want to use it as your system disk, you could use the VMSKITBLD BUILD option to build a new system disk on the RA90 disk.

The existing system disk is the source disk. The new disk is the target disk.

Caution

The VMSKITBLD BUILD option initializes the target disk, deleting all of its previous contents. For information on copying files to an existing system disk without destroying files, see Section 2.5.2.

If you want to build your operating system on another disk and you are not concerned about losing the current contents of the target disk, use the BUILD option as described in the following procedure.

How to Perform This Task

1. If the source disk is not the current booted system disk, boot the operating system from the source disk.
2. Log in to the SYSTEM account.
3. Make sure the disk is spun up and on line. If you are using a removable disk, you must also place the disk into the appropriate drive.
4. Enter the following command to invoke VMSKITBLD:VMSKITBLD prompts you to choose one of the following options:
5. Enter BUILD and press Return. VMSKITBLD displays messages that either prompt you for information needed to complete the operation or inform you of the procedure's status.
   1. In response to the following prompt, enter the name of the source disk:
   2. In response to the following prompt, enter the top-level system directory for the source disk:
      In most cases, you can choose the default value [SYS0].
   3. In response to the following prompt, enter the name of the target disk:
   4. In response to the following prompt, enter the volume label of the target disk:
   5. In response to the following prompt, enter the top-level system directory:
      In most cases, you can choose the default value [SYS0].
   6. The procedure displays the following message to warn you that the target disk will be initialized and to allow you to stop the procedure:
      Make sure it is safe to destroy the contents of the target disk, and enter Y to continue.
   
   When the system displays the dollar sign ($) prompt, the system disk is built. VMSKITBLD automatically dismounts the target disk. At this point, the target disk contains all the operating system files required for a complete system.
6. Complete the system disk by creating a rights database and network proxy database and configuring the system with appropriate system parameters. For instructions, see Section 2.5.1.1.
7. To use the new system disk, reboot the system with the new system disk.

Example

The following example runs VMSKITBLD.COM to build a new system disk. It copies the files on the current system disk to create a new system disk on the DUA0: disk.

2.5.1.1 Completing a System Disk Built with VMSKITBLD.COM

After you create a new system disk using the VMSKITBLD BUILD option, use the following procedure to complete the new system disk:

Opcom Activate Password Execution Download

1. Boot the new system disk using a conversational boot. For instructions, see the upgrade and installation supplement for your computer.
2. When the SYSBOOT> prompt appears, enter the USE DEFAULT command to boot with default values for all system parameters.
3. Enter the CONTINUE command to continue booting.
4. After the system boots, log in to the SYSTEM account. The password for the system account will be the default password, MANAGER. Make sure you change this password.
5. Use the Authorize utility to create a rights database and a network proxy database. For more information, see the OpenVMS Guide to System Security.
6. Run AUTOGEN from the SAVPARAMS phase to set appropriate values for system parameters. Be sure to specify the CHECK_FEEDBACK option. See Section 14.5 and the AUTOGEN section of the OpenVMS System Management Utilities Reference Manual for detailed information on running AUTOGEN.
   To reboot from the former system disk, specify REBOOT as the end phase when invoking AUTOGEN.
   To reboot the system from the new system disk, specify SHUTDOWN as the end phase and reboot manually, specifying the new system disk.

Example

Opcom Activate Password Execution Code

2.5.2 Using VMSKITBLD.COM to Copy System Files to an Existing Disk

You can use VMSKITBLD to copy the operating system files to a target disk without deleting the files already existing on the target disk. For example, if you accidentally delete a large number of system files from a system disk, you can use VMSKITBLD to copy the system files from another system disk.

Previous | Next | Contents |

Opcom Activate Password Execution Windows 10

[Home]

Opcom Activate Password Executions

| [Comments] | [Ordering info] | [Help]

Opcom Activate Password Execution Software

Copyright © Digital Equipment Corporation 1996. All Rights Reserved.