Browse Prior Art Database

Tool to improve the operability of IBM Content Manager OnDemand on z/Os or OS/390

IP.com Disclosure Number: IPCOM000014088D
Original Publication Date: 2003-Jun-19
Included in the Prior Art Database: 2003-Jun-19
Document File: 3 page(s) / 75K

Publishing Venue

IBM

Abstract

The present publication relates to IBM Content Manager OnDemand Version 7.1 in z/OS environment. This publication comprises two main parts : Part I : Some recommendations, hints and tips which are useful when one starts with IBM Content Manager OnDemand Version 7.1 in OS/390 or z/OS. This must be considered as an addendum to the technical documentation provided by IBM. Part II : The description of a tool to help the operations and the monitoring of the batch loading process in IBM Content Manager OnDemand Version 7.1.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 50% of the total text.

Page 1 of 3

Tool to improve the operability of IBM Content Manager OnDemand

on z/Os or OS/390

The present publication relates to IBM Content Manager OnDemand Version 7.1 in z/OS environement. This publication comprises two main parts : Part I : Some recommendations, hints and tips which are useful when one starts with IBM Content Manager OnDemand Version 7.1 in OS/390 or z/OS. This must be considered as an addendum to the technical documentation provided by IBM. Part II : The description of a tool to help the operations and the monitoring of the batch loading process in IBM Content Manager OnDemand Version 7.1. In the following sections, IBM Content Manager OnDemand Version 7.1 will be referred to as "OnDemand".

Part I : Recommendations, hints and tips.

This part gives some advices to avoid pitfalls when defining objects with the Administration program of OnDemand in OS/390 or z/OS environments. These recommendations are mainly based on the fact that people working in OS/390 or z/OS have strong habits and reflexes coming from the old wolrd of MVS (Multiple Virtual Storage) and also on the fact that OnDemand can be connected to RACF (Resource Access Control Facility) which has its own rules.

Recommendations about the names of Application Groups, Applications and Folders
Since OnDemand is built to run on multiple platforms, it allows to use lower case, accentuated or special characters. This is not always the case with OS/390 or z/OS components. When OnDemand is connected to RACF (via the security exit option), it is necessary to adopt the RACF rules which are more strict.

Don't use lower case characters because JCLs (Job Control Language) are commonly written in upper case. Don't use special characters (except hyphen), accentuated characters or spaces between words because this is not allowed by RACF. Begin the names of the objects with the functional application short name to allow a quick identification when there are a lot of objects in OnDemand. Use short names because these names are used in the parameters of the OnDemand utilities and the JCL restricts the length of these parameters to 100 characters. A good practice should be between 15 to 20 characters.

Recommendations about the names of the fields defined in the Application Groups The fields are defined at two levels in OnDemand : in the Application Groups and in the Folders. The fields defined in the Application Groups are used to define the DB2 tables and are not shown to the end-user. They have to follow the DB2 rules. On the contrary, the fields defined in the Folders don't have any technical usage. They are shown to the end user and should have a clear signification for them.

These recommendations apply only to the names of the fields defined in the Application

1

Page 2 of 3

Groups :

Use only upper case characters because this is more usual for MVS people. Don't use special characters (except underscore), accentuated characters or spaces between words because this is not allowed b...