Frequently Asked Questions

Below is a list of common questions we have received from BBCS clients regarding OpTech. If your question is not answered below, please email it to OpTech Sales.

Each client has 4 separate data environments: Production, Production-Training, Validation and Validation-Training.

When first migrating to OpTech, a client code is determined for each client. This 5 digit code (usually the ISBT facility code, i.e. W1234) is used to identify each client on the OpTech system. All user IDs, workstations, printers, libraries, etc will start with this code. This allows us to easily identify the owner of all objects on the system. Authority to your environments uses group profiles and is controlled at the object level.

Since all OpTech clients are sharing an iSeries, the iSeries value settings have to be the same for all OpTech clients. When determining these settings, BBCS requirements were followed and recommendations were taken into consideration. Settings that do not follow the BBCS recommendations were decided upon with the expertise of mindSHIFT.
OpTech is using software called Any Date from Help Systems which allows each client to function in their own time zone.
OpTech is utilizing a custom version of the BBCS Day-End program which allows multiple Day-End jobs to run at the same time. Every night, the system goes into a restricted state while the Day-End program for all clients run. This process takes about 20 minutes. After Day-End is finished, mindSHIFT starts the nightly backups, which take 15 minutes – 1 hour depending on the type of backup.
Production User IDs in #991 will not have to change, however OpTech requires a 7-10 character user ID for iSeries sign on. The first 5 characters are the facility’s unique ID, which is typically their ISBT number. The 6th character indicates the user’s environment and characters 7-10 are the user’s current production ID. When the user signs on, the last 4 characters are passed into the BBCS System which enables the production security definitions to be duplicated to the training environments.
The Client’s Authorized Representative completes a FRM2210 (User Account Request) for any activation, change or de-activation to their user profiles. This form is sent to the OpTech Cloud Coordinator who reviews the request and submits it to mindSHIFT. Once the request is completed, the signed FRM2210 is returned to the Client Representative.

Access to the BBCS system is managed by the Client using BBCS #991.

A CL is available to all OpTech clients to reset user’s passwords and to re-activate them if they get locked out. This CL needs to be added to your Utility Menu and access should be given using #991.
No, there should be no need. Activities that require command line access have either been transferred to OpTech or can be added to the BBCS menu as a custom CL.
Facilities using BBCS Primary can access their spool files through the Attention Key Menu.

Facilities on ABO Suite can access their spool files through #006 in ABO Express or through the Attention Key Menu in Controller.

All OpTech clients also have access to the IBM Navigator program, which includes spool file management tools.

Yes, Function #998 in the BBCS System allows for user call to UPDDTA (DFU). #998 will need to be added to your Utility Menu and you will need to give authorized users access to the function using #991. Function #998 only allows your users to update data in your data libraries.
There are no limits to the number of automated jobs you can request. To add / change / delete a scheduled job, the Client’s Representative sends the request to the OpTech Cloud Coordinator. The Cloud Coordinator will review the request to ensure it will not have a negative impact on the server. If approved, the Cloud Coordinator will work with mindSHIFT to get the scheduled job created and notify the client upon completion.
Each client is given one custom library. Additional libraries may have an additional cost. Before allowing a custom CL on the server, the Client must give OpTech written documentation of the purpose of the program and a list of all files and actions taken on the files (read, write, etc.). There may be an additional cost for reviewing and transferring the custom CLs depending on the number and complexity of the programs.
Yes – there is a function on the BBCS menu that gives authorized users access to Query. That access limits your users to querying only your data libraries.
OpTech users will have no command line access and therefor will not be able to develop custom programs on the OpTech system. Requests for custom CL programs can go to OpTech. All other requests for custom developed programs would have to go through BBCS and would likely have an additional charge.
Yes, journaling is allowed as long as it is limited to your data and custom object libraries. You will not be allowed to access any journals for other clients or for shared libraries / objects.
Through the Attention Key Menu in Controller/Primary, all OpTech clients have the ability to manage their printers (i.e. Start/End, Respond to Messages, Manage spool files).

If new IP printers are needed or a setting needs to be changed, the Client would contact the OpTech Cloud Coordinator. OpTech will also handle any updates to a workstation’s settings.

BBCS Implementation Services is required when

  • A client is implementing the BBCS system for the first time
  • A client is migrating to OpTech and upgrading to a new release in tandem.

BBCS Implementation Services is recommended when an existing OpTech client is upgrading to a new release.

BBCS Implementation Services is not needed when a client is migrating to OpTech without upgrading their BBCS software as OpTech will provide the Project Management services.

No, we will handle the change of OS during the migration.