The NoteBook of EricKong
  BlogJava :: 首页 :: 联系 :: 聚合  :: 管理
  611 Posts :: 1 Stories :: 190 Comments :: 0 Trackbacks

#

How do you search the directory for the members in the PDS Library?
To see the directory of a PDS Library, you need to type M against the name of the Partitioned Dataset(PDS). The M Command tells the MVS Operating System to display the directory of the Partitioned Dataset(PDS).

Suppose, you want to see the directory(List of all the members) of the Partitioned Dataset(Library) AGY0157.DEMO.SRCLIB. Then, type an M against its name in the DSLIST Utility ISPF Menu 3.4 screen.

Image91[1]

Upon hitting the Ctrl Button, you get to see the directory of the Partitioned Dataset(PDS) AGY0157.DEMO.SRCLIB – you can see the entire list of members in the PDS.

Image92[1]

Generally, you will keep your program, jobs, REXX scripts assorted in Libraries or Partitioned Datasets(PDS). Here, I have stored all my COBOL Programs in this library.
posted @ 2011-12-20 17:40 Eric_jiang 阅读(209) | 评论 (0) | 编辑 收藏

How do I find the file I want on Mainframes? How do you find/list files in ISPF?
You want to search and locate a file. Finding the file on MVS Operating System is done using, ISPF Menu 3.4, called Dataset List Utility. Go to ISPF Menu 3.4 screen, and type the name of the dataset that you want to search and hit Ctrl.

For example, if you want to search for the file AGY0157.EMPLOYEE.DATA, then type AGY0157.EMPLOYEE.DATA in Dsname field.

Image87[1]

Upon hitting the Ctrl button, you would find list of files displayed before. Note that, Dataset List Utility(DSLIST) works by searching for all files that match a pattern. So, when you type AGY0157.EMPLOYEE.DATA, what you actually specify is a pattern.

All files matching this pattern will be displayed. So, if there is a file – AGY0157.EMPLOYEE.DATA.MASTER, it also matches the pattern. Thus, it will also be listed.

Image88[1]

In fact, if you don’t know the exact name of your file, you can just specify the pattern followed by a wild-card. Say, for example, if you want to search for all the files starting with AGY0157.DEMO.something, then you can specify it as AGY0157.DEMO.*

Image89[1]

When you hit Ctrl, you would get the list of all datasets(files), whose names start with AGY0157.DEMO.

Image90[1]
posted @ 2011-12-20 17:30 Eric_jiang 阅读(177) | 评论 (0) | 编辑 收藏

While creating a new file in ISPF, how do I specify whether is Sequential file(PS), or a Partitioned Dataset(PDS)?
A sequential PS File doesn’t have any partitions or members(0 members). So, it doesn’t have a directory to look upto. Thus, the space allocated to a directory, in terms of Directory Blocks for a Sequential PS File is 0.

On the other hand, for Partitioned Dataset(PDS), it can contain 1 or more members. So, it needs a directory to record the whereabouts(location) of its members, which are scattered throughout the memory randomly. You need to allocate space in terms of Directory Blocks to a Directory in Partitioned Dataset(PDS). Thus, Directory Blocks for a PDS should be some finite number, say 5 blocks, or 10 blocks.

Suppose you are creating a new File AGY0157.EMPLOYEE.DATA. You specify the Directory Blocks on the ISPF Menu 3.2 screen, as follows -

1. If you want the file AGY0157.EMPLOYEE.DATA to be a Physical Sequential File(PS), then fill the Directory Blocks field = 0.

Image85[1]

2. On the other hand, if you want the file AGY0157.EMPLOYEE.DATA to be a Partitioned Dataset(PDS), having 1 or many members, and a directory, specify Directory Blocks field = 1,2,3 or ...(any finite value) blocks. In the figure below, I have put Directory Blocks = 5 Blocks.

Image86[1]
posted @ 2011-12-20 17:26 Eric_jiang| 编辑 收藏

What is a Partitioned Dataset(PDS)?
When you create a sequential dataset(PS), it occupies a large amount of storage space(minimum 50,000 bytes). Sometimes for doing trivial tasks,  storing only a few records, you would not be utilising the entire space available in a sequential file. Thus most of the space in the Sequential file is wasted and is blocked.

IBM provides a way to split or partition up the space in a sequential data-set. IBM Software engineers invented the Partitioned Dataset, often called PDS. Each part is called a Member. A Partitioned Dataset can have many members(parts). Each member behaves like a sequential file on it own.

How does the PDS then keep track of its members? A Partitioned Dataset(PDS) includes a directory(like a telephone directory), which is a diary or journal, where MVS Operating system keeps track of the members in a PDS. The members of a PDS can be scattered haphazardly anywhere in the vast computer storage space. Well-then, you consult the directory to find out the members in the PDS. Just like in a book, the index tells you, the keyword you are looking for, and the page no. where it can be found, the same way, the directory tells you the member name, and the computer memory address where you can find it. Thus, the directory maintains the list of member-names and pointers to the actual physical place in Computer Memory where they are stored.

Not just this, but the directory also keeps track of its statistics, like when each member was created, when was it last changed/viewed by somebody, how much space it occupies, which TSO-userid created it and bla bla..

On the Windows Operating System, we generally keep related files together in a folder. On the same lines, you keep related members together in one PDS. Thus, a Partitioned Dataset is Mainframes-counterpart of Folders on Windows Operating System. Folders contain many related files. A PDS contains many related members.

When create this special type of partitioned sequential file – Partitioned Dataset, you need to decide, how big its directory is going to be. The bigger the directory, the more no. of partitions(members) it will support. You express this in terms of Directory Blocks. Generally, 1 directory block can store information about 5 members. The directory always remains fixed, can’t grow bigger on the fly, so you need to careful when specifying the directory blocks, and you have to do it in advance.

Image84[1]
To sum up, a Partitioned Dataset(PDS) is a specialised type of sequential file, which is divided into members, each member being a sequential dataset by itself. Thus, a PDS acts like a library which houses several related files.
posted @ 2011-12-20 17:21 Eric_jiang 阅读(192) | 评论 (0) | 编辑 收藏

How do you create a file in ISPF?

ISPF organises most common functionalities that you need to perform on Mainframes – like creating a new file/folder, editing a file, searching for files, taking backup etc. in the form of menus, just like a Nokia Cellular Phone.

To create a new file, you have to go to the menu 3.2 in ISPF. You enter the dataset name here on ISPF Screen.


www.puyufanyi.com
posted @ 2011-12-20 16:59 Eric_jiang 阅读(162) | 评论 (0) | 编辑 收藏

How do you form Dataset Names?

In a Mainframe computer, there would be thousands of files(datasets). It is obvious, to name each Dataset differently. Mainframes support very large dataset names. In Mainframes, a dataset name can be 44 characters long in this format :
XXXXXXXX.XXXXXXXX.XXXXXXXX.XXXXXXXX.XXXXXXXX

You can form a dataset name by taking groups of upto 8 characters. Each of the group must start with a capital letter(alphabet).

Generally, it is a good practice to give meaningful names to your dataset. For example, if you are storing Employees data in a file, you can name it as EMPLOYEE.DATA

The MVS Operating System keeps track of groups of datasets by referring to their names, which are called Qualifiers. The first part of the dataset name is called High-level Qualifier(HLQ).

Generally, when you access or log-in to Mainframes, you are given a USER-ID, just as on Windows PC, you need a userid to login. Most professionals or software engineers who work in Mainframe Projects would have a TSO user-ID. When you use a TSO-id, a special requirement applies to most datasets(files) that belong to you.

Suppose your TSO-id is AGY0157, then all your datasets should have the High-level qualifier AGY0157. Thus, the files that belong to you should start with AGY0157. For example, the name of Employees file would be

AGY0157.EMPLOYEE.DATA

You must understand that, mostly in projects, you can identify the files that belong to you, your application or your system by seeing the High-level Qualifier.

In fact, Mainframes are also installed with Security Software(like RACF), that controls access to files by seeing the High-Level Qualifiers. Thus, although you can see your buddy’s files on a Mainframe, you cannot make any changes to it.

posted @ 2011-12-20 16:37 Eric_jiang| 编辑 收藏

What is ISPF?
ISPF stands Interactive System Productivity Facility. ISPF is more popular than TSO, because its an easier way to get things done in MVS without knowing most of the TSO Commands. Rather than typing out commands, you go through a series of menu – just like the Nokia Mobile Handset, to do tasks, like creating a new file, deleting a file, editing a file, renaming, copying, writing and submitting JOBs.
posted @ 2011-12-20 16:29 Eric_jiang 阅读(174) | 评论 (0) | 编辑 收藏

What is TSO?
TSO stands for Time Sharing Option. TSO is the part of MVS that lets you use the MVS System interactively. Just as from the DOS-Prompt, you type in commands to create a directory, remove a directory, create a new file in editor, type in data, copy files, rename files delete files, the same way, one can type commands on the TSO. When IBM first introduced TSO in 1969, interactive computing was a hot new feature, which required a large portion of the memory. This is where the O comes from : O meaning option, TSO was optional : when all jobs were run as batch jobs.

Since, it allows multiple users to share time on the system concurrently, it is Time Sharing.

You said, All JOBs are run as Batch JOBs. Then, what about TSO? Well, under the hood, each TSO user session is run as a Batch Job. It can specify the procedure to be executed or the command when the user LOGON occurs. It also specifies the Terminal Monitoring Program to monitor TSO User Session. It specifies the data-sets to be allocated, when the user logs on. When you write a Batch Job means, you write its JCL(What Input Data Set, What Output DataSet, Which Program to run). Who writes the JCL for TSO? The System Programmer guys who maintain TSO.

 

posted @ 2011-12-20 16:23 Eric_jiang 阅读(144) | 评论 (0) | 编辑 收藏

How to Split Strings in Java – 2 Examples

In this article we will see how to split string in Java both by using String’s split() method and StringTokenizer. If you have any doubt on anything related to split string please let me know and I will try to help.


String Split Example Java
Let's see an example of splitting string in Java by using split() function:

 

//split string example


String assetClasses = "Gold:Stocks:Fixed Income:Commodity:Interest Rates";
String[] splits = asseltClasses.split(":");


System.out.println("splits.size: " + splits.length);


for(String asset: assetClasses){
System.out.println(asset);
}


OutPut
splits.size: 5
Gold
Stocks
Fixed Income
Commodity
Interest Rates

In above example we have provided delimiter or separator as “:” to split function which expects a regular expression and used to split the string.
Now let see another example of split using StringTokenizer

//string split example StringTokenizer


StringTokenizer stringtokenizer = new StringTokenizer(asseltClasses, ":");
while (stringtokenizer.hasMoreElements()) {
System.out.println(stringtokenizer.nextToken());
}


OutPut
Gold
Stocks
Fixed Income
Commodity
Interest Rates


My personal favorite is String.split () because it’s defined in String class itself and its capability to handle regular expression which gives you immense power to split the string on any delimiter you ever need. Though it’s worth to remember following points about split method in Java


1) Some special characters need to be escaped while using them as delimiters or separators e.g. "." and "|".

 //string split on special character “|”

String assetTrading = "Gold Trading|Stocks Trading|Fixed Income Trading|Commodity Trading|FX trading";


String[] splits = assetTrading.split("\\|");  // two \\ is required because "\"     itself require escaping


for(String trading: splits){
System.out.println(trading);
}


OutPut:
Gold Trading
Stocks Trading
Fixed Income Trading
Commodity Trading
FX trading

 

 // split string on “.”
String smartPhones = "Apple IPhone.HTC Evo3D.Nokia N9.LG Optimus.Sony Xperia.Samsung Charge”;


String[] smartPhonesSplits = smartPhones.split("\\.");


for(String smartPhone: smartPhonesSplits){
System.out.println(smartPhone);
}


OutPut:
Apple IPhone
HTC Evo3D
Nokia N9
LG Optimus
Sony Xperia
Samsung Charge

2) You can control number of split by using overloaded version split (regex, limit). If you give limit as 2 it will only creates two strings. For example in following example we could have total 4 splits but if we just want to create 2 we can use limit.

 


//string split example with limit


String places = "London.Switzerland.Europe.Australia";
String[] placeSplits = places.split("\\.",2);


System.out.println("placeSplits.size: " + placeSplits.length );


for(String contents: placeSplits){
System.out.println(contents);
}


Output:
placeSplits.size: 2
London
Switzerland.Europe.Australia

To conclude the topic StringTokenizer is old way of tokenizing string and with introduction of split since JDK 1.4 its usage is discouraged. No matter what kind of project you work you often need to split string in Java so better get familiar with these API.

 

posted @ 2011-12-14 13:44 Eric_jiang 阅读(251) | 评论 (0) | 编辑 收藏

XMLAccess

As a WebSphere AppServer or PortalServer administrator, your world can be a constant learning curve as new applications come along that utilize different aspects of the IBM middleware platforms. You may, for example, have mastered the art of deploying portal configurations using full or partial portal exports. This is convenient and easy to do. However, it may not give you the flexibility required for that new upcoming portal application that is being conceived in the minds of your company's Java developers. Luckily for you, XMLAccess is quite flexible.

Assuming you are familiar with the basic concepts of XMLAccess, the following refinements to the process should be straightforward. Instead of taking a full export from your production environment, suppose you wish to only export the portlets? In XMLAccess, the portlet is represented by the object type "web-app." Naturally you could generate an export of the portlets using the following XML (which is included in the samples shipped with Portal):


<?xml version="1.0" encoding="UTF-8"?>
<request xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="PortalConfig_1.3.xsd" type="export">
    <portal action="locate">
        <web-app action="export"
          objectid="*"/>
    </portal>
</request>
By importing this xml file, we direct the portal to export only the web-app object called '*' which is a wildcard for all web-apps. The command would be as follows:


xmlaccess.bat -in C:\temp\export_all_portlets.xml -user wpsadmin -pwd wpsadminpwd -url http://portal.example.com/wps/config -out C:\temp\outputfile_all_portlets.xml

Right, so very easy. However, this sort of thing is useful only if we already have a portal configured with all of the portlets. If we're exporting all "web-app" objects, this assumes we have some to export in the first place. Suppose you have 50 new portlets that all need to be installed, but you have no existing portal that has all of them in place. Are you going to use the portal admin interface and click-click-click your way through installing 50 portlets, assigning permissions, creating pages, putting the portlets on the pages, etc. etc. etc.? Probably not - at least, I know I wouldn't.

How can we use XMLAccess to build a portal configuration if we are deploying portal elements for the very first time? This task won't involve exporting a config from somewhere, since we don't have things configured in any environment yet. Instead we're going to construct our XML files from scratch and import them into a blank portal in order to build our configuration.

The various XML files referred to from this point forward are printed at the end of this article.

The Blank Portal
When installing WPS, it is often desirable to deploy the portal without the sample pages and labels and portlets; it is simply too much clutter. To install a blank portal, use the following command when invoking the installation program:


install.bat -W installPortlets Sequence.active="false"

Proceed through the portal install sequence as you normally would. When complete, start the portal and go the portal home page. You should now see the blank portal.

Before continuing, be sure to have all of your necessary files in place. That is, if you are installing a theme, place the folder containing the theme on the PortalServer in the correct location. The same goes for skins, portlet WARs, etc.

Theme folders go into:
C:\WebSphere\AppServer\installedApps\<nodename>\wps.ear\wps.war\themes\html\

Skin folders go into:
C:\WebSphere\AppServer\installedApps\<nodename>\wps.ear\wps.war\skins\html\

By default, portlet WAR files need to be placed in:
C:\WebSphere\PortalServer\installableApps

With our blank portal installed, and with our component files in place, let's begin constructing our new portal. We'll start with the skins and themes.

Install Skins and Themes
The XML to install the theme will of course include the standard XML header for WPS 5.1. After that, we will do the required locate action on the "portal" object. After this we will instruct XMLAccess to perform an "update" on our skin with the parameters that we specify as show in Listing 1.

The skin object we specified includes the objectid, uniquename, and resourceroot parameters. Objectid will be the skin's referential id within the portal database. For ease of use, we also have a uniquename specified for this skin so that we can easily refer to the skin from this point forward. The resourceroot indicates the case-sensitive folder name of our skin that we placed in the skins\html\ directory.

Let's save this file as import_skins.xml. Once we import this file, we will have installed the skins into our portal:


xmlaccess.bat -in C:\temp\import_skins.xml -user wpsadmin -pwd  wpsadminpwd -url http://portal.example.com/wps/config

To install our themes, we need an XML file with similar information 

 

Since a theme has default and allowed skins assigned to it, we first have to find these skins before we can assign them to the theme. So we do a 'locate' on our two skins that were added in Listing 1. Once we find them, we perform an "update" on the theme object.

The update uses defaultskinref to define the default skin for the theme. For the first theme, we used Skin_A as the default skin. The objectid and uniquename for the theme are defined (and can be different, as indicated). The resourceroot is the case-sensitive folder name of the themes\html\ directory.

Notice that in addition to defining the default skin for each theme, we can also define the other skins that can be used with this theme. Notice that for Theme_Blue we are using Skin_A as the default, but we allow Skin_A as well as Skin_B. This is defined in the <allowed-skin skin="..."> section. Notice that for Theme_Green we are using Skin_B as the default and we only allow that skin. After all, Skin_A is red. Mixing a red skin with a green theme is just plain ugly.

Now let's save the xml file as import_themes.xml and import our themes into the portal configuration:


xmlaccess.bat -in C:\temp\import_themes.xml -user wpsadmin -pwd wpsadminpwd -url http://portal.example.com/wps/config
Install Portlets
We have our themes and skins imported, now let's put those pesky portlets in place.

Constructing the XML file for portlet install is a little trickier. It involves knowing some key information about the portlets. This information is found in the portlet.xml and web.xml inside the portlet.war file. For this step Winzip is especially useful, as you will need to be able to open the portlet WAR file (see Listing 3). You may also be able to get this info from the portlet developer. After all, he can see this info in his portal toolkit inside WebSphere Studio. However, developers being as busy as they usually are, good luck extracting this info from them.

Okay. This is slightly more complex. Here we have 3 portlets that we're installing. You can see we're locating the portal (of course), and then we do an update on object "web-app" which represents the WAR file.

The next parameter is the web-app uid parameter. The uid must match the uid attribute of portlet-app in portlet.xml in the portlet WAR file.

Following the uid, we have to specify the location of the portlet WAR file. When we transferred our portlet WARs to the server, we placed them in C:\WebSphere\PortalServer\installableApps. To refer to this location, we can use the $server_root$ variable which gets set when the XMLAccess interface is invoked.

Next, we have to perform an update on the portlet-app object. This represents the portlet application and is the parent of all the portlets contained within. The next parameter is the portlet-app uid parameter. The uid must match the uid attribute of concrete-portlet-app in portlet.xml in the portlet WAR file.

Finally we have the update to be performed on each portlet in the portlet application. In this example we only have one portlet in each WAR file, but we could potentially have several in each one. If this were the case, we'd have multiple "portal" objects defined within the "portal-app" object. We give the portlet an objectid and we define the name. The portlet name parameter must match the content of the portlet-name subtag of concrete-portlet in portlet.xml in the portlet WAR file.

So let's go ahead and save the xml file as import_portlets.xml and execute:


xmlaccess.bat -in C:\temp\import_portlets.xml -user wpsadmin -pwd wpsadminpwd -url http://portal.example.com/wps/config

 

 

We should now have deployed skins, themes, and portlets. Let's create a page and drop some portlets on it.

Create Pages
This is very straightforward. We need pages on which to place our portlets. Pages and labels are represented in the XML files as "content-node." Seems pretty logical if you think about it. A node of content. A content-node. Brilliant.

Our XML will look like Listing 4. Think of it logically. We first locate the resources we need (themes, portlets) and then we create our pages using those resources. Piece of cake. In this example, we'll create a label in the Content Root called Home (Content Root is the highest node of the content hierarchy. It exists by default). Hanging off this label is a single page called Welcome. On this Welcome page is single row containing our portlet, PortletCharlie.

You can see that we start off by locating the necessary resources - first the theme, Theme_Blue and then the portlet, PortletCharlie. Finally we have to locate the Content Root.

The next step in the process is to create the Home label. We give it an objectid and a uniquename. We define the content-parentref to be this label's immediate parent. In our case, this is the objectid of Content Root. Because we're creating a label at this point and not a page, we can assign a theme to the label. So we define themeref to be Theme_Blue.

Once created, we must immediately "locate" the new label before it can be used in the rest of the XML file. Next, we want to create the page called Welcome that is on the label called Home. You can see the values we use to define this page. With a page, however, we can also define the columns and rows containers that compose the structure of a portal page. Within these containers, we place the portlets.

The rows and columns on the page are defined in the "component" section in that page. In this example, within the page definition for the content-node Welcome, we define a component with an orientation of "H," which stands for horizontal, which is therefore a row. Setting the orientation to "V" would of course create a column. Rows can contain columns and vice versa. Tweaking these settings is how you could create an incredibly complex nested row/column page structure, if you so chose.

There are other parameters you can tinker with. Changing "ordinal" will change the order in which this content-node appears (since we only have one content-node at this level, it doesn't matter, but if we had a whole row of pages on the toolbar, we could order them using the ordinal parameter). Setting the "active" parameter to false would de-activate this content-node; and on and on...


<component action="update" active="true"  objectid="container1" ordinal="-1" orientation="H"  type="container" width="300">
 <portletinstance   action="update" handle=""  objectid="portletinstance1"portletref="Portlet_Charlie"></portletinstance>
</component>
Inside the component definition for the row on our page, you can see that we have put a portletinstance object with portletref set to Portlet_Charlie. This value must match the uid of the portlet that you wish to put in this container.

So here it is. Let's save this file as import_pages.xml and execute:


xmlaccess.bat -in C:\temp\import_pages.xml -user wpsadmin -pwd wpsadminpwd -url http://portal.example.com/wps/config
Once our import is complete, fire up a browser and go check out your brand new portal! Wunderbar! You should see your label with a page that has a portlet on it. Experiment.

Of course you can also go further and assign permissions to your objects using XML, or you could create XML files to remove portlets but leave the pages and so forth and so on.

Make liberal use of the example files in C:\WebSphere\PortalServer\doc\xml-samples, or the InfoCenter documents regarding XML Access. These pages are currently located at http://publib.boulder.ibm.com/infocenter/wp51help/topic/com.ibm.wp.ent.doc/wps/admxmlai.html.

 


posted @ 2011-11-25 13:13 Eric_jiang 阅读(405) | 评论 (0) | 编辑 收藏

仅列出标题
共57页: First 上一页 36 37 38 39 40 41 42 43 44 下一页 Last