Shadowing the SNADS Directory

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

Brief: Although it is advantageous to have specific directory entries for each remote user, synchronizing directories among machines is difficult if done manually. You can use *ANY entries in the directory to represent remote users, but this approach has disadvantages. This article describes the system- provided, directory shadowing capability. Shadowing lets you automatically synchronize directories and maintain remote-user entries on your machine with data from each home machine.

The system directory on each AS/400 contains entries for users local to that machine and for selected users on other AS/400s. In addition to being used for SNADS distributions, the directory is used with OfficeVision. The directory includes data about users, departments, and locations.

Directory entries can be either specific or generic. A specific entry contains a user ID, address, and system name. SNADS can immediately verify the user ID and address of a specific entry in your system directory before sending the distribution.

A generic entry contains *ANY in the user ID, or user ID and address parts. Generic entries are useful when you need to be able to send distributions to remote users, but you don't want to add specific remote users to your directory. If SNADS does not find the specific directory entry and cannot use a generic entry, the distribution is not sent. You are notified of the faulty user ID and address with out incurring any communications overhead. With a generic entry, SNADS sends the distribution to the remote system, which then checks for the user ID and address. You are still notified if you use an incorrect user ID and address but only after incurring the greater communications overhead.

Ideally, all remote users to whom you send distributions or mail have specific directory entries on your system. That way, the send programs can validate the intended recipient locally. The problem is that it can be extremely difficult to manually maintain directory entries for remote users on your system. To do that, you need a procedure to monitor any changes in the remote directory, so that users who are remote to you are added as local users. You have to replicate the changes in the remote directory in your local directory. This procedure has to be followed for each system to which you send distributions. You need to perform the directory maintenance at each of the remote systems.

Rather than face the horrible job of manually synchronizing directories, many administrators simply choose to use the generic *ANY entries. After all, one *ANY entry can represent a number of remote users. This approach is workable but not optimal because of possible communications overhead due to errors.

Alternatively, you can use the system-provided, directory shadowing function. With directory shadowing, you can collect directory entries from other systems and add them to your system directory. You can then supply your directory entries to other systems. Shadowing is designed to be run periodically, so any changes to directory entries on remote systems will be applied to your directory soon after they are made.

Shadowing Concepts

Although shadowing is concerned with the system directory, which is used by SNADS and OfficeVision, it operates independently of those products. All that is needed is an APPC connection between machines that will shadow their directories (the machines can be in an APPN network).

Shadowing uses the terms supplier and collector to describe the relationship of machines to each other. At your local system, you indicate those machines that supply their directory information using their machine names. Those remote systems are supplier systems. Your machine, in turn, is regarded by each of the suppliers as a collector system-i.e., your machine collects directory information from them. A machine can be both a supplier and a collector. For example, you may want two AS/400s to shadow each other's directory. Each machine is a supplier because it supplies its directory entries to the other machine. Each machine is also a collector because it collects directory entries from the other machine.

You can designate any number of other machines as suppliers to your machine. A remote machine cannot send directory entries to your machine through directory shadowing until you identify it as a supplier. At a remote site, no command can be used to force its directory entries onto your machine. Similarly, any number of other machines can have a collector relationship to your machine. You can either accept collectors by default or create a list of authorized collector machines.

In addition to defining the supplier and collector relationships; you set options to control when shadowing occurs; the number of retries in the event of errors during shadowing; which directory entries are modified in your directory from remote systems; which directory entries are shadowed from your directory to a remote system; and whether or not remote entries within your directory are supplied to remote machines.

Shadowing supplies all directory information with the exception of the mail indicator field, print cover page field, indirect user field, user profile, nickname, and distribution lists. After the initial load, shadowing only sends directory changes to the collector system. Directory changes include additions, deletions, and modifications to directory, department and location information. Changes to the IBM-supplied directory entries QSECOFR, QSYS, QDFTOWN, QLPAUTO, QLPINSTL, and QUSER are never shadowed from one system to another.

Get Set to Shadow

The actual shadowing process is trivial; in fact, after setting it up correctly, shadowing is automatic and runs as a background task. There are two difficult parts of shadowing: setting up your system and its suppliers so you get the directory entries you want, and completing and understanding the first shadow event. 1 lists the steps you take use to start shadowing another system's directory.

The actual shadowing process is trivial; in fact, after setting it up correctly, shadowing is automatic and runs as a background task. There are two difficult parts of shadowing: setting up your system and its suppliers so you get the directory entries you want, and completing and understanding the first shadow event. Figure 1 lists the steps you take use to start shadowing another system's directory.

Shadowing maintains your directory by applying changes that occurred in other directories based on the date and time of those changes. Coordinating system timestamping of changes to directory entries is important, particularly when shadowing from several systems. Shadowing uses the timestamp value to determine which directory change to use. If the entry was changed on more than one system, the most recent change is applied. To coordinate system timestamping, you set the Universal Time Coordinated Offset system value (QUTCOFFSET). This value is used to timestamp changes to directory entries so that the system can determine which changes are the most recent, even across time zones. (For more information, see the article, "Automate Daylight Saving Time Changes," MC, March 1994.)

Next, you use the Change Directory Attributes (CHGDIRA) command to set the values used in shadowing. (Although it's called "change," this command functions like an edit command, in that you are shown the current values, and you can work with them.) You need to consider several parameters: the verification and supplier programs, the retry interval and limit, the message queue, and shadow remote users. The CHGDIRA command display is shown in 2.

Next, you use the Change Directory Attributes (CHGDIRA) command to set the values used in shadowing. (Although it's called "change," this command functions like an edit command, in that you are shown the current values, and you can work with them.) You need to consider several parameters: the verification and supplier programs, the retry interval and limit, the message queue, and shadow remote users. The CHGDIRA command display is shown in Figure 2.

You can use the verification program (VRFPGM) and supplier program (SUPPGM) parameters to identify programs you write to control directory shadowing. The parameter lists and the return codes used with these programs are documented in the System Programmer's Interface Reference. These programs are optional; if supplied, they are called when changes are made to your directory. You can include any required logic in the programs to accept or reject a proposed change to your directory.

The verification program is called before any changes are made to a directory entry, department, or location information. You can use the verification program to reject a proposed change from another system's directory. An important use of the verification program is to verify and reject the remote directory entries supplied to your system. On the supplier system, a remote directory entry may be an entry that is local to your system-the remote entry system's directory describes one of your users. Rather than accept its version of your user, you might choose to reject the remote entry. You use this defense mechanism in conjunction with the shadow remote users (RMTSHD) parameter of the CHGDIRA command, described later. If you rely solely on the RMTSHD setting, you may not be able to control the directory entries supplied.

The opposite of the verification program is the supplier program. You may want to use this program to filter out directory entries that are intended strictly for local use on your system; entries for temporary employees, for example. This program monitors your directory when it is called upon to be a supplier to a remote system. Whenever a directory entry is modified, it becomes a conadidate for shadowing. The supplier program can reject an entry before it is supplied to the remote system.

Although the frequency of shadowing is set in other commands, you control shadowing retries with the retry interval (RTYITV) and retry limit (RTYLMT) parameters of the CHGDIRA command. These parameters are used to indicate what to do if there is an error during the shadowing process. Examples of errors include inactive communications (the line not being varied on), disconnects during the shadowing process, or a power failure on either system.

You should change the message queue (MSGQ) parameter from the default value of QSYSOPR before starting shadowing. That way, you can easily review the messages after the shadowing process is complete. The messages indicate the date and time shadowing started and ended, the number of directory entries that were shadowed, and any errors encountered with shadowed data.

The last parameter on CHGDIRA, shadow remote users (RMTSHD), is one of the most important parameters in the entire shadowing process. The RMTSHD parameter asks whether or not remote user directory entries should be shadowed to other systems. (A directory contains entries for users who are local and remote to your system. The remote entries in your system are local entries on the other system.) The default is to not shadow remote user data from one system to another. You may not want to rely entirely on the RMTSHD parameter setting because the value could be inadvertently changed by an unknowing system administrator at the remote site. You may need the protection of a verification program to keep your local user entries safe from updates sent from other systems.

The Initial Load

To start shadowing, identify the systems that will be suppliers to your system and perform an initial load from the suppliers' directories. You identify the systems and specify how to perform the initial load with the Add Directory Shadow System (ADDDIRSHD) command. You can also use the Work with Directory Shadow Systems (WRKDIRSHD) command, which includes options to add, change, remove, and display shadowed systems, in addition to options to suspend and resume shadowing.

The ADDDIRSHD command, shown in 3, includes four main groups of parameters. These parameter groups are used to identify the remote system that is to be a supplier, the schedule of shadowing, the initialization option, and miscellaneous parameters.

The ADDDIRSHD command, shown in Figure 3, includes four main groups of parameters. These parameter groups are used to identify the remote system that is to be a supplier, the schedule of shadowing, the initialization option, and miscellaneous parameters.

The first group of parameters includes the system name (SYSNAME) parameter, which specifies the remote system. This parameter should name another AS/400 to which you already have an APPC connection. You can further identify the system using the remote location name (RMTLOCNAME) and remote network ID (RMTNETID). Unless you have made changes to the network attributes on the remote machine (using the CHGNETA command), you will probably be able to use the default values for RMTLOCNAME and RMTNETID.

Parameters in the second group describe the shadowing schedule. You can request shadowing on an hourly, daily, weekly, biweekly, or monthly basis. You should select a schedule based upon the volatility of your directories and the importance of keeping your directories synchronized. The default value is *WEEKLY. Because shadowing runs as a communications job it creates overhead on your lines. You want to select a frequency that does not create undue drag on your system or the remote system.

You use the initial shadow (INZ) parameter to describe how you intend to load directory entries from the shadowed system the first time. During the initial shadow, all of the directory information from the shadowed system is used. Subsequent shadowing only sends changes. You can load the directory manually or with the APPC communication link.

If the directory you want to shadow is huge (several thousand entries), and you don't want to incur the overhead of a potentially long communications session, or if you do not yet have the APPC link, you may want to load the directory manually. The Copy From Directory (CPYFRM-DIR) command creates a tape or diskette file of directory entries on the supplier system. On the collector system, you use the Copy To Directory (CPYTODIR) command to load the directory from the tape or diskette.

If you manually shadow the directory, you specify either *NONAPPC or *COMPLETED for the INZ parameter. *NONAPPC means that you intend to manually shadow the directory, but have not yet done so. If you use *NONAPPC, be sure that you use the CPYTODIR command to load the diskette or tape before the next scheduled shadow event. You need the directory entries on your machine so that any changes that occurred on the supplier system after the CPYFRMDIR command can be applied. *COMPLETED means that you have completed the CPYFRMDIR and CPYTODIR process prior to using the ADDDIRSHD command and you are ready to start shadowing.

The alternative method to load your directory is to use *APPC as the parameter value. This value means you want the initial shadow event to run as a communications job. You indicate when the initial shadow event is to occur using the scheduled date and time parameter (SCD). The default value for this parameter is *CURRENT, which indicates your system will attempt to start the initial shadow event immediately. You can set a specific date and time for the initial shadow event if you prefer.

The INZ parameter also contains a replace data option with values of *YES or *NO. The default value, *NO, means a duplicate directory entry from another system will not replace the entry on your system. *YES means the entry from the other system replaces your entry.

The miscellaneous parameters include the communications mode (MODE), the local location name (LCLLOCNAME), and text describing the shadowed system. You should be able to use the default values for MODE and LCLLOCNAME. You should supply text; it is available for review on the WRKDIRSHD display.

At this point, you've added a supplier to your system. Shadowing that supplier system will happen at the specified date and time (immediately if you used *CURRENT for the scheduled date and time). Shadowing runs as a job in the QSYSWRK subsystem, which I'll describe next.

The Shadowing Process

After the initial load, shadowing runs automatically based on the frequency value that you set for the system to be shadowed. You can shadow any number of other systems, each of which has its own frequency.

Shadowing runs in the QSYSWRK subsystem. When QSYSWRK starts, an autostart job entry starts job QDIRSHDCTL if any systems are identified as suppliers to your system. The QDIRSHDCTL job then submits additional jobs to QSYSWRK to shadow the suppliers when the scheduled shadow date and time arrives. If subsystem QSYSWRK is active before you define any system to be shadowed, you can start the QDIRSHDCTL job with the Start Directory Shadowing (STRDIRSHD) command.

When the date and time for shadowing a system arrives, QDIRSHDCTL starts another job in QSYSWRK. The job name is the name of the system being shadowed. That job assumes an APPC connection is active, and a session is available to the remote system. The shadowing job will not activate the communications link between the two systems.

During shadowing, if any errors occur with a directory entry, messages are sent to the message queue identified in the CHGDIRA command. If the shadowing job ends abnormally, a job log is written. You should make it a habit to review the message queue and check for a job log after each shadowing event.

Controlling and Monitoring Shadowing

Once you define your supplier systems and do the initial load from each system, shadowing runs as a background job. Your primary control point is the WRKDIRSHD command. You have the option to select whether to work with supplier systems or collector systems.

The supplier option lists all of the systems you identified as supplying directory entries. In addition to the name, the current status, number of attempts, and date and time of the next shadow event are shown. For successful shadow events, the status is COMPLETED. If you review the display when shadowing is being done, the status is IN PROCESS. If any errors occurred during the shadowing, the status is ERROR. An error status applies to the job itself, not to any errors with directory entries.

You can select options for each shadowed system on the display. You can force shadowing to occur before the next scheduled date and time by selecting the change option and resetting the next scheduled shadow.

Shadowed systems can also be suspended and resumed on the WRKDIRSHD display. For example, if you know that a communications line will not be available during a scheduled shadow session, you can suspend shadowing and resume it later.

The second option of WRKDIRSHD lets you work with collector systems or systems that shadow your directory. This is a simpler display than the display for supplier systems. The only options you have for systems are to add additional collectors or to remove a collector. You normally do not have to add collectors; a collector is automatically added to this list the first time it shadows your system. However, a setting on the collector display lets you control collectors. The "check authority when shadowing" option defaults to 'N', meaning that any other system that contacts your system through APPC is allowed to shadow your directory. If you set the check authority option to 'Y', then another system can only shadow your system if it is in the list of collectors shown on the display. If you set the option to 'Y', you need to manually add new collector systems; the collector systems won't be able to add themselves to your system as collectors.

The Shadow Knows

Directory shadowing is the simplest way to maintain directories among systems. You don't need to do much addtional work to start shadowing, since the process uses the same communications link that other processes between systems use.

You should review the documentation in the Distribution Services Network Guide to understand your options when you are shadowing among many systems. You do not necessarily want every system to have supplier and collector relationships with every other system. That situation can lead to unnecessary shadowing and the possibility of losing synchronization.

If your directories are small or if you are satisfied using *ANY directory entries, then you may decide not to use directory shadowing. But if you are maintaining large directories and need them available across an enterprise network, you should investigate shadowing, starting with a few systems and extending it as far as required.

Craig Pelkie can be reached through Midrange Computing.

References Communications: Distribution Services Network Guide (SC41-9588, CD-ROM QBKA1B02). Programming: Work Management Guide (SC41-8078, CD-ROM QBKA9J02). System Programmer's Interface Reference (SC41-8223, CD-ROM QBKA8402).

Shadowing the SNADS Directory

Figure 1 Steps to Shadow Another System's Directory

 1. Verify that you have an APPC connection to the other system, and that the connection is active. 2. Consider setting system value QUTCOFFSET if the systems are in different time zones. 3. Use the Change Directory Attributes (CHGDIRA) command on your machine to set values for the verification program, the retry interval and limits, and the message queue. 4. Use the CHGDIRA command on the other machine to set values for the supplier program and to shadow remote users. 5. Use the Add Directory Shadow System (ADDDIRSHD) command on your machine to add the remote system as a system to be shadowed. 6. Initialize the directory shadow, either with the APPC connection or with the Copy from Directory (CPYFRMDIR) and Copy to Directory (CPYTODIR) commands. 7. Use the Start Directory Shadowing (STRDIRSHD) command on your machine to start the directory shadowing job QDIRSHDCTL in subsystem QSYSWRK, if necessary. Once shadowing is set up, the Work with Directory Shadow Systems (WRKDIRSHD) command can be used to control shadowing activities. 
Shadowing the SNADS Directory

Figure 2 The CHGDIRA Command

Shadowing the SNADS Directory

Figure 3 The ADDDIRSHD Command



Support MC Press Online





  • Mobile Computing and the IBM i

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

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

    Get your copy today!

  • Automate IBM i Operations using Wireless Devices

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

    Order your copy here.

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


    Download your free copy of DR Strategy Guide for IBM i from Maxava today.


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

    SB Profound WP 5539

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

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

    Read Node.js for Enterprise IBM i Modernization Now!


  • 2020 IBM i Marketplace Survey Results


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

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

  • AIX Security Basics eCourse

    Core Security

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

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


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

    Profound Logic Software, Inc.

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

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

  • What to Do When Your AS/400 Talent Retires

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

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

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


  • IBM i Resources Retiring?

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


  • Backup and Recovery Considerations for Security Data and Encrypted Backups

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

  • Profound.js: The Agile Approach to Legacy Modernization

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


  • Data Breaches: Is IBM i Really at Risk?

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

    Watch the webinar today!


  • Easy Mobile Development

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


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

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

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

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

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

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

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

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

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

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

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

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

    Download and watch today!


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

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

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


  • Accelerating Programmer Productivity with Sequel


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

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

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

  • Business Intelligence is Changing: Make Your Game Plan

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

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

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


  • Controlling Insider Threats on IBM i

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

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

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

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

  • How to Manage Documents the Easy Way

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

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


  • Lessons Learned from the AS/400 Breach

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

  • Overwhelmed by Operating Systems?

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

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

    This presentation includes a live demo of Network Server Suite.


  • Real-Time Disk Monitoring with Robot Monitor

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

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



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

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

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

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


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

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

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

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


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

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

    • Capture
    • Manage
    • And distribute documents digitally


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


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

    Are there still companies that use AS400? Of course!

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

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


  • Ask the RDi Experts

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

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

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


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

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

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



  • Inside the Integrated File System (IFS)

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

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

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


  • Expert Tips for IBM i Security: Beyond the Basics

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

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

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



  • 5 IBM i Security Quick Wins

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

  • How to Meet the Newest Encryption Requirements on IBM i

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

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



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

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

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

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



  • Fight Cyber Threats with IBM i Encryption

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

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




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

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

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


  • How to Transfer IBM i Data to Microsoft Excel

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

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

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



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

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

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

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



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

    SB Profound WC GenericHave you been wondering about Node.js? Our free Node.js Webinar Series takes you from total beginner to creating a fully-functional IBM i Node.js business application.
    Part 1 will teach you what Node.js is, why it's a great option for IBM i shops, and how to take advantage of the ecosystem surrounding Node.
    In addition to background information, our Director of Product Development Scott Klement will demonstrate applications that take advantage of the Node Package Manager (npm).
    Watch Now.

  • The Biggest Mistakes in IBM i Security

    SB Profound WC Generic The Biggest Mistakes in IBM i Security
    Here’s the harsh reality: cybersecurity pros have to get their jobs right every single day, while an attacker only has to succeed once to do incredible damage.
    Whether that’s thousands of exposed records, millions of dollars in fines and legal fees, or diminished share value, it’s easy to judge organizations that fall victim. IBM i enjoys an enviable reputation for security, but no system is impervious to mistakes.
    Join this webinar to learn about the biggest errors made when securing a Power Systems server.
    This knowledge is critical for ensuring integrity of your application data and preventing you from becoming the next Equifax. It’s also essential for complying with all formal regulations, including SOX, PCI, GDPR, and HIPAA
    Watch Now.

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

    SB CYBRA PPL 5382

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

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

    Request your trial now!

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

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

  • Manage IBM i Messages by Exception with Robot

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

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

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

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

  • Hassle-Free IBM i Operations around the Clock

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

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

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

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