Can Robot/ALERT send text messages to cell phones?
Yes. Use Robot/GUIDE to help you set up a TCP/IP vendor. It works just like sending e-mail to any e-mail address with Robot/ALERT.

I have a job that runs every day. On certain days when the job completes, I want a Robot/SCHEDULE job to react to its completion. Can I create a reactive job and specify which days I want it to run?
If you have a reactive job and days to run specified, Robot/SCHEDULE looks for both conditions before it runs the reactive job. Therefore, if the prerequisite job completes and it is a day the reactive job is scheduled to run, Robot/SCHEDULE runs it.

If the prerequisite job does not run, the reactive job will not run. If the reactive job has a day and time specified, and the prerequisite job has not run, you get a W (warning) status on the reactive job indicating that, “Not all prerequisites have been met.”

How do I make a script run when I open a SEQUEL dashboard?
There are two ways to make a script run in a SEQUEL dashboard: automatically, or by pressing a button. Either way, you must add an Action Button to your dashboard.

1. Create a new dashboard or open an existing dashboard in design mode.

2. Select Insert > Action Button from the menu.

3. In the Action Button dialog, press the SEQUEL Object button and navigate to your script.

4. To make the script run when the dashboard is opened, check the “Autorun” box. (If this box is not checked, you must press the Action Button to run the script.)

Message groups are used in Robot/CONSOLE as a way to group messages into logical categories based on the source of the message. You can use message groups to separate certain messages from normal system messages. For example, you might create a message group to group messages by specific applications, by programming groups, or by company department.

By grouping messages, you easily can redirect a message based on where it came from without having to create a message set to process the message.

You determine the types of messages that should be separated into message groups and the grouping criteria to use. You then define each message group and its selection criteria.

When a message arrives on a message queue monitored by Robot/CONSOLE, the message groups are checked in the priority order specified. If a match to a message group’s selection criteria is found, the message group is assigned to the message. Note: Only one message group can be assigned to a message.

How to create and use a message group
In this example, all EDI message failures are captured and directed to the local expert, Jean, without creating or using a message set.

1. Before creating the EDI message group, you must create an EDI message center. From the Robot/CONSOLE Main Menu, select option 6, System Setup Menu. When the System Setup Menu displays, select option 1, Message Center Maintenance. When the Message Center Maintenance panel displays, press function key 6, Add Record, to create a new center.
   
2. When the Message Center Entry panel displays, create the new message center. In this example, Jean is the expert in the EDICENTER Message Center. When Robot/CONSOLE receives an EDI error, it displays a pop-up window to advise her of the problem that needs attention. If Jean does not respond to the pop-up window after one minute, the error is redirected to the broadcast list, DALELIST. DALELIST sends pager or e-mail messages to Jean and several of her co-workers (via Robot/ALERT) until the error is answered or the end of the list is reached.
3. Create the EDIGRP message group. Go to the Maintain Message Groups panel and press function key 6 to create a new group. Name the group EDIGRP and give it a message priority, such as 25. Add a description and redirect failure messages directly to the local Message Center, EDICENTER. Press Enter to create the new group.
   
4. When the Maintain Message Groups panel displays, enter option 2, Message Group Detail, next to the new EDIGRP message group.
   
5. When the Message Group Detail panel displays, add the Message File and Library information. This creates a filter so that the message group will pick up only EDI errors.
   
6. Activate the message group.

You have created a process that will capture EDI failure messages and direct them to the local EDI expert without needing a message set.

Message groups are a powerful feature of Robot/CONSOLE. If you haven’t tried them, we hope this article helps you think about ways you could start using them!

Contributed by Bill Broeckert, Technical Consultant

Robot/SAVE’s RBSDUPROT command comes to the rescue

Does your company have a legal, industry, or policy requirement to maintain duplicate copies of your backup records? If so, you’ll be interested in a new command RBSDUPROT that was added recently to Robot/SAVE.

This command duplicates a Robot/SAVE tape rotation and cross-references the duplicate to the original tape. You can tell what is on each tape because Robot/SAVE automatically maintains a record for you, helping you get away from error-prone manual methods of tracking duplicates. In addition, this cross reference helps satisfy auditor requirements for reliable tracking of duplicate records. Best of all, because Robot/SAVE knows how to handle multi-volume data, there’s no problem when your backup data spans tapes.

Before you begin
To use the RBSDUPROT command, you must have the following:

• Robot/SAVE 11.08 or higher installed on your system
• Two drives of the same type that use the same media

To help you manage duplicated volumes, select option 11, Tape Cross Reference Inquiry, on the Save Media Management Menu to display volume information for both the duplicate and the original volumes. Press function key 8 to print a report of your duplicate volume information. The Volume Inquiry panel also displays duplicate volume information.

Duplicating volumes using the RBSDUPROT command is considered an ad hoc operation. If you want to release the duplicated volumes to the scratch pool when their data expires, make sure to specify Y (Yes) in the Release expired Ad hoc tapes to scratch field on the Media Defaults panel.

When you submit or schedule the RBSDUPROT command, both the RBSDTALIB and RBSPGMLIB libraries must be in your interactive library list. The command is located in RBSPGMLIB, but uses files from RBSDTALIB. If you are scheduling the RBSDUPROT command using Robot/SCHEDULE, display the Control Options panel and enter RBSPGMLIB/RBSJOBD in the Job Description fields, and *JOBD in the Library List Name field.

Using the RBSDUPROT command

The following describes the fields in the RBSDUPROT command.

• Backup Class/Backup Set. Enter the backup class and backup set to which the volume you want to duplicate currently is attached.
• Rotation code. Enter the rotation code of the volume to be duplicated. To enter a specific rotation code, enter the code with leading zeroes. Specify *LASTRUN to select the last rotation used by Robot/SAVE.
• From device. The From device is the device where the original volume is mounted. Enter the name of a device, or specify *SAME to use the same device Robot/SAVE used to save the data.
• To device. The To device is the device used for the duplicate volume. Enter a device name, or specify *DEVGRP to use a device in the same group as the original device where the data was saved.
• To volume identifier. The To volume identifier is the volume to use for the duplicate volume. You can enter the name of a volume; *SCRPOOL to select a volume from the Robot/SAVE scratch pool; or *MOUNTED to use the volume that currently is mounted. Note: If you are using an Automated Media Librarian (AML), the only valid value is *SCRPOOL (scratch pool).
• File expiration date. You can specify an expiration date for the duplicate volume. Enter a date using your system date format. Enter *FROMFILE to use the same expiration date as the original volume. Enter *PERM if the duplicate volume is permanent, with no expiration date.

Contributed by Theresa Aleckson, Technical Consultant

How do your queries access Oracle, MySQL, SQL, and other databases?

Do you need to combine System i, UNIX, and Windows data all on one executive dashboard panel? Do you need to consolidate data from multiple databases in your network? Are you tired of being forced to transfer System i data from your DB2/400 database to a data warehouse so that it can be queried?

The basic i5/OS Query product allows you to access only your local DB2 data through the queries you write. IBM’s new Web Query tool also allows you to access your DB2 data, but it costs extra to use and connect to other databases. In addition, you have to go somewhere else for support for these connections. Other tools allow you to access DB2 data on your System i, but they do it from Windows or UNIX. Wouldn’t it be nice to have a System i-centered solution?

SEQUEL connects to remote databases—FREE
SEQUEL allows you to access DB2/400 databases, along with access to Oracle, MySQL, Microsoft SQL Server, and other JDBC type 4 databases. SEQUEL makes it easy to create connections to these databases. Best of all, end users never have to know that they are viewing data from another system, or building a dashboard that presents data from multiple sources.

For example, you can combine data from Oracle, SQL Server, and DB2 into a single executive view (see Figure 1). With SEQUEL, your team can access other servers for no additional charge.

How easy is it to connect?
The SEQUEL Administrator makes it easy to set up connections to other databases. You just enter the system name, or IP address, along with a user ID and password. Once the connection has been configured, any

SEQUEL user can manually point to the defined database (see Figure 2). Or, users can set up their defaults so they always access the selected database. With SEQUEL, users can simply build a view and choose the files they want to use, without worrying where they are located.

How easy is it to add tables?
To see a list of tables you can query, simply click on the file list (see Figure 3). Just as you can with DB2 files, it’s easy to select the tables you need to create new views, tables, drill downs, summarized graphs, reports, and more from your non-System i data.

Our support team can show you how easy it is to use SEQUEL to solve your database access issues. Call us at 1-800-328-1000 to request a live demo or a FREE 30-day trial in your own network of databases. Or, you can download and view an archived presentation on this topic.

Contributed by Tom Huntington, Vice President of Technical Services

Help/Systems, the world’s leader in automated operations and business intelligence for the IBM System i, announces the acquisition of the eveLogic Group in both Europe and Asia Pacific. EveLogic has many years of experience working with Help/Systems to market and support Help/Systems products across Europe from its companies in the United Kingdom and France, as well as across the Asia Pacific region through its Australian subsidiary.

Janet Dryer, Chief Executive Officer of Help/Systems said: “We are very excited at the opportunity to add eveLogic to the Help/Systems family. EveLogic has an excellent reputation for its service and support and we look forward to building on this reputation as we go forward.”

Konrad Litwin, Managing Director of eveLogic, added, “This represents a fantastic opportunity to expand the Robot products to customers in every region of the world. Our emphasis has always been to provide the best products to automate each customer’s environment and to back that up with the best support in the industry. Going forward, our customers will continue to see the same level of local support from the same people they’ve come to know. It’s what we’ve always done, and will continue to do under the Help/Systems name.”

With this acquisition, Help/Systems plans to offer even more opportunities for its customers by establishing a stronger presence worldwide. That includes conducting Web-based seminars in the local language, a larger presence at trade shows and user conferences, more on-site training and support, and the opportunity for users to learn more about all Help/Systems products.

Jim Cassens, Help/Systems’ Vice President of International Sales, said, “I look forward to working with Konrad and his team in expanding our presence in the international marketplace. In addition, Help/Systems will continue to work with and support our other distributors located around the world.”

All my SEQUEL reports are printing duplex. How do I change that?
You can turn off duplex printing by changing the SEQUEL/SQLPRT1 printer file. Use the following Change Print File (CHGPRTF) command:

CHGPRTF FILE(SEQUEL/SQLPRT1) DUPLEX(*NO)

I want to use Robot/ALERT to send e-mail messages, but my System i is not configured as an e-mail server. Is there a way around this?
Your System i doesn’t have to be an e-mail server for Robot/ALERT to send e-mail messages. If you use Robot/GUIDE for Automated Vendor setup, you simply specify the domain name or IP address of your SMTP e-mail server in the Outbound TCP/IP Host field. If you are using a two-way e-mail connection, specify the domain name or IP address of your POP3 e-mail server in the Inbound TCP/IP Host field.

I use Robot/SCHEDULE. When I set up a reactive job, it runs as soon as it gets the completion code for its prerequisite job. I would like the reactive job to wait a little while before it runs. How would I set this up?
You can attach OPAL code to the reactive job to do this. The OPAL must be submitted before the reactive job runs. Here’s an example that would delay the job for one minute. This code checks that the reactive job is not in a delayed status and then adds one minute until it will be submitted.

Users are raving about Robot/SCHEDULE’s new job monitors

Robot/SCHEDULE Job Monitors are designed to help you identify job schedule problems. You specify the jobs you want to monitor for the following Job Monitor events:

* A job that runs too long

* A job that completes too fast to have run properly

* A job that starts later than its scheduled time

The Robot/SCHEDULE 10 job monitors help you monitor critical jobs for specific events such as jobs that run too long, complete too quickly, or start later than scheduled. (Click on the thumbnail above to enlarge.)

When a Job Monitor event occurs, Robot/SCHEDULE can end the job automatically and notify you by sending a message to the job’s message queue; sending a text, e-mail, or pager message via Robot/ALERT; or sending a status to the Robot/NETWORK Status Center.

If the message queue specified on the Robot/SCHEDULE Control Options panel for a job is a message queue monitored by Robot/CONSOLE, the Job Monitors also can interface with Robot/CONSOLE.

Contributed by Jeanne Thiesfeld, Technical Consultant

In 2008, U.S. Daylight Saving Time begins on March 9 and ends on November 2. Whether you change the time manually or have the system change the time automatically, the most important thing to keep in mind is that Robot/SCHEDULE must be inactive when the time change is made.

Two ways to set up the time change
Basically, there are two ways to accomplish the time change in Robot/SCHEDULE.

1. Create a CL program to end Robot/SCHEDULE, change the time, and restart Robot/SCHEDULE. (You can set up a Robot/SCHEDULE job to call this program.) This approach is explained in the Help/FACTS “Using Robot/SCHEDULE to automate Daylight Saving Time change.”

Note: You can modify the program to restart additional products so they pick up the time change. Products that benefit from this include: Robot/ALERT, Robot/AUTOTUNE, Robot/CLIENT, Robot/CONSOLE, Robot/MONITOR, Robot/NETWORK, and Robot/REPORTS.

2. Use the QTIMZON system value to make the change. With this approach, you need to create two Robot/SCHEDULE jobs to make Robot/SCHEDULE inactive during the time change. Download the Help/FACTS “Using Robot/SCHEDULE with the QTIMZON System Value” to get the details.

Important note: If you use the QTIMZON system value, IBM has issued the following Program Temporary Fixes (PTFs) that add updated time zone descriptions. After you apply the appropriate PTFs for your OS level, you can change the QTIMZON system value to the new value for your region. Continue to check with IBM in the event that future PTFs become available.

* i5/OS V5R4M0: PTFs SI26040 and SI25990

* i5/OS V5R3M0: PTFs SI26039 and SI25991

There are no changes for the QTIMZON system value in V6R1M0.

If your system uses a Hardware Management Console (HMC), you might need to apply additional fixes.

Unless specifically mentioned above, other Robot products are not affected by the time change. In addition, SEQUEL, ABSTRACT, ESEND, and EASY VIEW are not affected by the time change.

Contributed by Jeanne Thiesfeld, Technical Consultant

Expands job monitoring, comparisons, and more!

Help/Systems, the world’s leader in automated operations and business intelligence software for the IBM System i, announces the release of Robot/SPACE 3.0, the newest version of its software that automatically monitors and manages IBM System i disk space. Robot/SPACE eliminates disk storage crises by notifying users of potential trouble and provides tools for quickly finding disk storage problems.

Robot/SPACE job monitoring has been expanded to allow users to monitor the storage allocated by their QTEMP libraries and spooled files for active jobs on their system. All three job monitors can track detail information for every threshold exception, and can be configured using Robot/GUIDE.

With Robot/SPACE 3.0, users can compare two collections from the same collection group and list the libraries, objects, IFS directories, IFS files, output queues, or file members that have changed from one collection to the other.

Robot/SPACE 3.0 includes role-based security to authorize users for using specific product functionality or accessing specific data. The administrator can add, edit, delete, and copy roles, as well as assign users to specific roles.

Users can use On-Demand Reporting to quickly create ad hoc reports of collected records. These reports can be saved as an HTML, text, or PDF file for viewing, printing, or distributing.

For more information about the new release, contact your Help/Systems Regional Sales Manager at 1-800-328-1000 (U.S. and Canada), or your local distributor.

Related PDFs that may of interest

1. Robot/SPACE 3.0 Enhancements

2. Robot/SPACE 3.0 Comparison Checklist

3. Instructions for converting from Robot/SPACE Version 2.0 to Version 3.0

Give developers and administrators access without losing control of security

How much authority do your developers and administrators need on your production systems? Does each programmer need *ALLOBJ authority? Have you ever failed a security audit because of too many user profiles with too much special authority? When end users call your Help Desk for help with authority problems, does the Help Desk ask for the end user’s password and then sign on to test the authority issue?

Robot/SECURITY handles *ALLOBJ security issues
Robot/SECURITY can help you handle all of these issues. Robot/SECURITY is actually five security products in one package: Exit Point Monitoring, QAUDJRN Monitoring, Security Auditing, Forensics, and Profile Exchange. With Profile Exchange, a user can “swap” to a different profile, on demand, at any time. The Robot/SECURITY Administrator defines all Profile Exchange users and their access schedules.

The administrator can review all requests
At your option, the Robot/SECURITY Administrator can preview profile exchange requests and approve or deny them using e-mail, an i5/OS message, or Robot/SECURITY.

Robot/SECURITY logs all profile exchange activity
Robot/SECURITY provides a comprehensive log of profile exchange activity, including the requester and the activity associated with the request. At the end of a profile exchange session, Robot/SECURITY automatically e-mails the user’s activity log to the Robot/SECURITY Administrator. Anyone who needs to can view the detail online, or in a printed report, and can use the Exchange Audit History List panel to drill into QAUDJRN records to review the events of the exchange activity.

Call 1-800-328-1000 today to request a FREE demo or a FREE 30-day trial of Robot/SECURITY.

Contributed by Tom Huntington, Vice President of Technical Services