AIX (Advanced Interactive eXecutive) is an operating system developed by IBM for business all across the world that needs data metrics that can keep up with the ever-changing scope of business in today’s world. AIX is a version of UNIX. AIX is designed to work on a number of computer platforms from the same manufacturer. On its launch, the system was designed for IBM’s RT PC RISC workstation.
AIX was developed with Bourne Shell
as the default shell for three versions of the OS. Afterwards, it was changed
to KornShell going forward from version 4. The OS uses Common Desktop
Environment (CDE) as the default user interface for graphics. The System
Management Interface Tool on the OS allows users to access the menu using a
hierarchy of commands instead of the command line.
The operating system works on a number of hardware platforms. The initial OS was designed for the IBM RT PC and used a microkernel that controlled the mouse, disk drives, keyboard, and display. This allowed users to use all these components between operating systems by the use of a hot key-the alt+tab combination. The OS was also fitted on newer systems such as the IBM PS/2 series, IDM mainframes, AI-64 systems and can also be used with the Apple’s server network. AIX is commonly used on IBM’s 64-bit POWER processor and systems. AIX can run most Linux applications (after recompiling) and has full support for Java 2.
Since its introduction to computer infrastructure, the operating system has undergone a lot of upgrades with five versions released since 2001. The latest version of the software is the AIX 7.2. All of these come with a high tech security system and fast uptimes.
As an operating system AIX has become popular with students who learn quickly by working on AIX projects live. Working professionals have also been attracted by the dependability of the system and the intuitive that is part of its design.
End of Support for IBM InfoSphere Information Server 9.1.0
IBM InfoSphere Information Server 9.1.0 will reach End of Support on 2018-09-30. If you are still on the InfoSphere Information Server (IIS) 9.1.0, I hope you have a plan to migrate to an 11-series version soon. InfoSphere Information Server (IIS) 11.7 would be worth considering if you don’t already own an 11-series license. InfoSphere Information Server (IIS) 11.7 will allow you to take advantage of the evolving thin client tools and other capabilities in the 2018 release pipeline without needing to perform another upgrade.
IBM Support, End of support notification: InfoSphere Information Server 9.1.0
I had a reason this week to perform a substring on a character in Netezza this week, something I have not had a need to do before. The process was not as straightforward as I would have thought, since the command is explained as a static position command, and the IBM documentation, honestly, wasn’t much help. Knowing full well, that text strings are variable having to provide a static position is not terribly useful in and of itself. So, we need to use an expression to make the substring command flexible and dynamic.
I did get it work the way I needed, but it took two commands to make it happen:
The First was the ’instr’ command to identify the field and character I wanted to substring on: instr(<<FIELD_NAME>>,’~’) as This provides the position number of the tilde (~).
The second was the ‘substr’ command in which I embedded the ‘instr’ command: substr(<<FIELD_NAME>>,0,instr(<<FIELD_NAME>>,’~’) )
This worked nicely for what I needed, which was to pick out a file name from the beginning of a string, which was delimited with a tilde (~)
Substring on a Character Command Format
This format example starts with position zero (0) as position 1 of substring command and goes to the first tilde (~) as position 2 of the substring command.
, instr(<>,’~’) as pos2
, substr(<<FIELD_NAME>>,0,instr(<<FIELD_NAME>>,’~’) ) as Results
IBM Knowledge Center, Home, PureData System for Analytics 7.2.1, IBM Netezza database user documentation, Netezza SQL basics, Netezza SQL extensions, Character string functions
While investigating a recent Infosphere Information Server (IIS), Datastage, Essbase Connect error I found the explanations of the probable causes of the error not to be terribly meaningful. So, now that I have run our error to ground, I thought it might be nice to jot down a quick note of the potential cause of the ‘Client Commands are Currently Not Being Accepted’ error, which I gleaned from the process.
Error Message Id
An error occurred while processing the request on the server. The error information is 1051544 (message on contacting or from application:[<<DateTimeStamp>>]Local////3544/Error(1013204) Client Commands are Currently Not Being Accepted.
Possible Causes of The Error
This Error is a problem with access to the Essbase object or accessing the security within the Essbase Object. This can be a result of multiple issues, such as:
Object doesn’t exist – The Essbase object didn’t exist in the location specified,
Communications – the location is unavailable or cannot be reached,
Path Security – Security gets in the way to access the Essbase object location
Essbase Security – Security within the Essbase object does not support the user or filter being submitted. Also, the Essbase object security may be corrupted or incomplete.
Essbase Object Structure – the Essbase object was not properly structured to support the filter or the Essbase filter is malformed for the current structure.
IBM Knowledge Center, InfoSphere Information Server 11.7.0, Connecting to data sources, Enterprise applications, IBM InfoSphere Information Server Pack for Hyperion Essbase
While chasing an error to which only applied to join type stages, I thought it might be nice to identify what the InfoSphere Information Server DataStage / QualityStage are. There are three of them, as you can see from the picture above, which are the:
And, Merge Stage.
All three stages that join data based on the values of identified keycolumns.
IBM Knowledge Center, InfoSphere Information Server 11.7.0, InfoSphere DataStage and QualityStage, Developing parallel jobs, Processing Data, Lookup Stage
When you are controlling a chain of sequences in the job stream and taking advantage of reusable (multiple instances) jobs it is useful to be able to pass the Invocation ID from the master controlling sequence and have it passed down and assigned to the job run. This can easily be done with needing to manual enter the values in each of the sequences, by leveraging the DSJobInvocationId variable. For this to work:
The job must have ‘Allow Multiple Instance’ enabled
The Invocation Id must be provided in the Parent sequence must have the Invocation Name entered
The receiving child sequence will have the invocation variable entered
At runtime, a DataStage invocation id instance of the multi-instance job will generate with its own logs.
This approach allows for the reuse of job and the assignment of meaningful instance extension names, which are managed for a single point of entry in the object tree.