By default, the subsystem QINTER allocates all devices by workstation type?not by name. The purpose of this is to capture and allocate all devices regardless of the naming convention used. As you go about configuring your system, you may wish to allocate workstations by subsystems other than QINTER. The following information can be found in the OS/400 Work Management V3R1 (SC41-3306, CD-ROM QBKLAG00):
? When a subsystem starts, it attempts to allocate all workstation devices in the subsystem description. There is no hierarchy regarding device names versus device types.
? If the device is varied off, the subsystem cannot allocate it. The system arbiter (QSYSARB) holds a lock on all devices that are varied off.
? If the device is varied on and is not allocated by another subsystem, then the subsystem can allocate it and display the sign-on display.
? If the device is allocated by another subsystem and is at the sign-on display (i.e., no active job), the second subsystem can allocate the device from the first subsystem.
? If the device is varied off and all subsystems have started before you vary on the device, and if more than one subsystem could potentially allocate the device, it is unpredictable which subsystem will actually allocate it.
To avoid the situation of unpredictability, you can do one of the following things:
? Do not use workstation type entries in any subsystem?use only workstation name entries. This means removing the
workstation type entries from the IBM-supplied subsystem descriptions. Use the Remove Workstation Entry (RMVWSE) command. You can enter workstation name entries using generic prefixes (e.g., DSP*).
? Vary the workstation on when the system is started by specifying ONLINE(*YES) in the device description for the workstation. The subsystem that allocates the device is determined by the order in which the subsystems start.
? You can add workstation entries to a subsystem description, which causes the subsystem to allocate the device or not allocate the device.
To include the device, use this command:
ADDWSE SBSD(xxx/sbsd) + WRKSTN(dev) AT(*SIGNON)
To exclude the device, use this command:
ADDWSE SBSD(xxx/sbsd) + WRKSTN(dev) AT(*ENTER)
The AT(*ENTER) parameter keeps the subsystem from allocating the device at subsystem startup, but allows you to use the Transfer Job (TRFJOB) command to transfer the job after subsystem startup.
? Steve Bisel
More than ever, there is a demand for IT to deliver innovation. Your IBM i has been an essential part of your business operations for years. However, your organization may struggle to maintain the current system and implement new projects. The thousands of customers we've worked with and surveyed state that expectations regarding the digital footprint and vision of the company are not aligned with the current IT environment.
TRY the one package that solves all your document design and printing challenges on all your platforms. Produce bar code labels, electronic forms, ad hoc reports, and RFID tags – without programming! MarkMagic is the only document design and print solution that combines report writing, WYSIWYG label and forms design, and conditional printing in one integrated product. Make sure your data survives when catastrophe hits. Request your trial now! Request Now.
Forms of ransomware has been around for over 30 years, and with more and more organizations suffering attacks each year, it continues to endure. What has made ransomware such a durable threat and what is the best way to combat it? In order to prevent ransomware, organizations must first understand how it works.
Disaster protection is vital to every business. Yet, it often consists of patched together procedures that are prone to error. From automatic backups to data encryption to media management, Robot automates the routine (yet often complex) tasks of iSeries backup and recovery, saving you time and money and making the process safer and more reliable. Automate your backups with the Robot Backup and Recovery Solution. Key features include:
Business users want new applications now. Market and regulatory pressures require faster application updates and delivery into production. Your IBM i developers may be approaching retirement, and you see no sure way to fill their positions with experienced developers. In addition, you may be caught between maintaining your existing applications and the uncertainty of moving to something new.
IT managers hoping to find new IBM i talent are discovering that the pool of experienced RPG programmers and operators or administrators with intimate knowledge of the operating system and the applications that run on it is small. This begs the question: How will you manage the platform that supports such a big part of your business? This guide offers strategies and software suggestions to help you plan IT staffing and resources and smooth the transition after your AS/400 talent retires. Read on to learn:
LATEST COMMENTS
MC Press Online