PeopleTools 8.50 RVP Available

FYI, Oracle has made available PeopleTools 8.50 RVP (Release Value Propositions) - Click Here to read the Oracle blog.

Some notable PeopleTools 8.50 Enhancements are:

• Partial Page Refreshes using AJAX technology
• Menu Navigation (menu 2.0) by providing a new AJAX-enabled left navigation menu pagelet
• Search Page Enhancements by providing an option to specify the maximum number of rows returned
• Change Assistant enchancement by allowing parallel file deployment
• Extending Support for 64-bit Technology by providing supports to only 64-bit Operating Systems
• Securing Server Based File Directories by de-coupling PS_HOME so that executables, logs, and configuration files will no longer be contained in the same place
• Number of exciting new enhancements in Integration Broker

There are n number of interesting enhancement in PeopleTools 8.50... For complete information - read Oracle blog here

PROCESS GROUP

Process group is crucial in securing the processes and jobs in the system. It is possible to restrict access to certain processes within PeopleSoft by establishing process groups. A batch process is assigned a 'Process Group' when created. That 'Process Group' is then linked to a permission list (PL). The PL is then assigned to a 'Role' and, subsequently, to a USERID. Process groups are collections of process definitions that you create using PeopleSoft Process Scheduler.

Navigations to Assign a Process to a Process Group:

PeopleTools -> Process Scheduler -> Processes -> Process Definition Option Tab -> Process Security section

Navigations to Assign a Process Group to a Permission List:

PeopleTools -> Security -> Permissions & Roles -> Permission -> Process tabs -> Process Group Permissions

Users can run only the processes that belong to process groups assigned to their roles. For example, you may have a set of process definitions that relate to your Human Resources department and another set for your Manufacturing department. If process 'P1' is in the process group 'PG1' and any of the Permission List (PL) of the user, say 'USER1', does not have access to that process group 'PG1' - then - that user 'USER1' cannot run the process 'P1'. A process definition can be a member of multiple process groups.

The process group are not stored in any setup table of its own. They are stored in the table - PRCSDEFNGRP and PRCSJOBGRP (where process and job definitions are stored). If you look at the prompt for PRCSGRP field in those tables, it is a 'PROMPT WITH NO EDIT' - It means, you can keep adding new Process groups on the fly, on process and job definition components. You may want to execute below queries for better understanding:

select * from PS_PRCSDEFNGRP
select * from PS_PRCSJOBGRP

PsCIA - PeopleCode & File Pre-Processors

DDL for Tables created by PeopleCode & File Pre-Processors:

You must run the PeopleCode pre-processor to generate the database tables that Change Impact Analysis reads and analyzes.

The PeopleCode pre-processor generates two tables:
• PSCIAPCXREF
• PSCIAPCXREFTIME

You must have permission to create, delete from and write to these files. If you have full privileges, you can create these files prior to using Change Impact Analyzer.

****************************************************************************************************************
Note. Database administrators may consider assigning user IDs and passwords that grant read-only access to the database. However, users need create and write access to these work tables used by Change Impact Analyzer.
****************************************************************************************************************

The File Pre-processor generates the following database tables that Change Impact Analysis reads to perform analysis.
• PSFILEPROCESSRUN
• PSSQLXREFDEFN
• PSSQLXREFITEM
• PSFILESQLXREFDEFN
• PSFILEXREFDEFN

Note. You must have permission to create, delete from and write to these files. If you have full privileges, you run the pre-processor and create these files beforehand. DDL for above tables for DB2/Unix, DB2/OS390:

-- Table 1 - PSCIAPCXREF

CREATE TABLE OWNERID.PSCIAPCXREF (
PROGSEQ INT NOT NULL
,REFOBJECTID1 SMALLINT NOT NULL
,REFOBJECTVALUE1 CHAR(60) NOT NULL
,REFOBJECTID2 SMALLINT NOT NULL
,REFOBJECTVALUE2 CHAR(60) NOT NULL
,REFOBJECTID3 SMALLINT NOT NULL
,REFOBJECTVALUE3 CHAR(60) NOT NULL
,REFOBJECTID4 SMALLINT NOT NULL
,REFOBJECTVALUE4 CHAR(60) NOT NULL
,REFOBJECTID5 SMALLINT NOT NULL
,REFOBJECTVALUE5 CHAR(60) NOT NULL
,REFOBJECTID6 SMALLINT NOT NULL
,REFOBJECTVALUE6 CHAR(60) NOT NULL
,REFOBJECTID7 SMALLINT NOT NULL
,REFOBJECTVALUE7 CHAR(60) NOT NULL
,OBJECTID1 SMALLINT NOT NULL
,OBJECTVALUE1 CHAR(60) NOT NULL
,OBJECTID2 SMALLINT NOT NULL
,OBJECTVALUE2 CHAR(60) NOT NULL
,OBJECTID3 SMALLINT NOT NULL
,OBJECTVALUE3 CHAR(60) NOT NULL
,OBJECTID4 SMALLINT NOT NULL
,OBJECTVALUE4 CHAR(60) NOT NULL
,OBJECTID5 SMALLINT NOT NULL
,OBJECTVALUE5 CHAR(60) NOT NULL
,OBJECTID6 SMALLINT NOT NULL
,OBJECTVALUE6 CHAR(60) NOT NULL
,OBJECTID7 SMALLINT NOT NULL
,OBJECTVALUE7 CHAR(60) NOT NULL
)
IN

-- Table 2 - PSCIAPCXREFTIME
CREATE TABLE OWNERID.PSCIAPCXREFTIME (
LASTRUN CHAR(120)
)
IN

-- Table 3 - PSFILEPROCESSRUN
CREATE TABLE OWNERID.PSFILEPROCESSRUN (
LASTREFRESHDTTM TIMESTAMP
,FPPSTATUS CHAR(10) NOT NULL
)
IN

-- Table 4 - PSSQLXREFDEFN
CREATE TABLE OWNERID.PSSQLXREFDEFN (
XREF_ID CHAR(128) NOT NULL
,XREF_SQLTYPE CHAR(1) NOT NULL
,DBTYPE CHAR(1) NOT NULL
,XREF_GROUPBY_CNT SMALLINT NOT NULL
,XREF_ORDERBY_CNT SMALLINT NOT NULL
,XREF_HAVING_CNT SMALLINT NOT NULL
,XREF_SUBQUERY_CNT SMALLINT NOT NULL
,XREF_OUTERJOIN_CNT SMALLINT NOT NULL
,LASTUPDDTTM TIMESTAMP
,SQLTEXT LONG VARCHAR
)
IN

-- Table 5 - PSSQLXREFITEM
CREATE TABLE OWNERID.PSSQLXREFITEM (
XREF_ID CHAR(128) NOT NULL
,XREF_SQLTYPE CHAR(1) NOT NULL
,DBTYPE CHAR(1) NOT NULL
,XREF_ITEMSEQ SMALLINT NOT NULL
,XREF_ITEMTYPE CHAR(4) NOT NULL
,XREF_RECNAME CHAR(30) NOT NULL
,XREF_VALUE CHAR(128) NOT NULL
,XREF_USAGE CHAR(4) NOT NULL
,XREF_CLAUSE CHAR(5) NOT NULL
)
IN

-- Table 6 - PSFILESQLXREFDEFN
CREATE TABLE OWNERID.PSFILESQLXREFDEFN (
SOURCE_FILE CHAR(40) NOT NULL
,FILE_TYPE CHAR(4) NOT NULL
,XREF_ID CHAR(128) NOT NULL
)
IN

-- Table 7 - PSFILEXREFDEFN
CREATE TABLE OWNERID.PSFILEXREFDEFN (
SOURCE_FILE CHAR(40) NOT NULL
,CALLED_FILE CHAR(40) NOT NULL
,FILE_TYPE CHAR(3) NOT NULL
)
IN

PeopleTools Tables

A quick guide to PeopleTools Tables:
Projects:
* PSPROJECTDEFN — Project header table
* PSPROJECTITEM — Definitions in the project

Fields:
* PSDBFIELD — Fields in the system
• PSXLATITEM — Translate Values

Records:
* PSRECDEFN — Record header table
* PSRECFIELD — Fields in the record (subrecords not expanded)
* PSRECFIELDALL — Fields in the record (subrecords expanded)
* PSKEYDEFN — Indexes

Pages - (Named as Panels in the PeopleTools Tables Names)
* PSPNLDEFN — Page header table
* PSPNLFIELD — Page controls
* PSPNLHTMLAREA — Static HTML Areas on Pages

Components - (Named as Panel Group in the PeopleTools Tables Names)
* PSPNLGRPDEFN — Component header table
* PSPNLGROUP — Pages in the components

Menus:
* PSMENUDEFN — Menu header table
* PSMENUITEM — Items (components) on the menu

Security:
* PSCLASSDEFN — Permission List header table
* PSAUTHITEM — Menu items granted security by permission lists
* PSROLEDEFN — Role header table
* PSROLECLASS — Permission Lists in roles
* PSOPERDEFN — User ID header table
* PSROLEUSER — Roles granted to users

Portal:
* PSPRSMDEFN — Content References and Folders

Change Control:
* PSCHGCTLHIST — shows history of locked definitions with project name, incident, and description
* PSCHGCTLLOCK — shows definitions that are currently locked

Application Engine:
* PSAEAPPLDEFN — header record; 1 row per app engine
* PSAEAPPLSTATE — state records assigned to app engines
* PSAEAPPLTEMPTBL — temp tables assigned to app engines
* PSAESECTDEFN — sections
* PSAESTEPDEFN — steps
* PSAESTEPMSGDEFN
* PSAESTMTDEFN — actions

HTML Definitions:
* PSCONTDEFN — header record; last update time, etc.
* PSCONTENT — stores actual text in the HTML definition

Process Scheduler Related Tables:
* PSPRCSRQST
* PSPRCSQUE
* PSPRCSPARMS
* PS_PRCSRQSTDIST
* PS_MESSAGE_LOG
* PSPRCSRQSTTEXT
* PS_MESSAGE_LOGPARM
* PSPRCSRQSTXFER
* PS_CDM_LIST

All these tables should be in sync.

Configuring Report Manager - List/Explorer

Here I'll try to describe an approach to setup Report Manager - List/Explorer in PeopleTools 8.48. This is not a compherensive explaination... It, however, may help you understand basic approach.

Report Manager is a utility in PeopleSoft to view Reports from a different place than Process Monitor. Navigation: Reporting Tools -> Report Manager. It has fours pages: List, Explorer, Administration and Archives.

PSDSTSRV generates a message after a process gets posted in process monitor in order to display reports in Report Manager - List and Explorer page. Hence Integration Broker setup needs to be done and PUB/SUB App Server Processes required to be up and running. Here are the configuration steps:

- Navigate to PeopleTools -> Integration Broker -> Integration Setup -> Service Operations

- IB needs to be configured for four services

• PSRF_FOLDER_CREATE
• PSRF_REPORT_CREATE
• PSRF_REPORT_DATE_CHANGE
• PSRF_REPORT_DELETE

- Open Service Operation PSRF_FOLDER_CREATE and make it active in General tab.

- In Handlers tab add a handler and make it Active. Handler name might differ from the screenshots's name but the Application Class definitons must match. Package name is same as the service operation name.

- In Routings tab, add a routing definition and make it active. Not sure, but I think only one routing definition must be active at a time... Sender and Receiver node are the local nodes - in my case it is PSFT_HR... to confirm your local node, go to PeopleTools -> Integration Broker -> Integration Setup -> Nodes and search for node...

- Repeat the above activity for rest of the services PSRF_REPORT_CREATE, PSRF_REPORT_DATE_CHANGE, and PSRF_REPORT_DELETE also. Configuration is almost similar e.g., make the service active in general tab, Add a new handler and make it active (class id would differ for all) in handler tab, Add a new Routing Name and make it active in Routings tab.

You might want to navigate PeopleTools -> Integration Broker -> Integration Setup -> Routings / Services to check your routings or Services definition and status.

Here completes IB configuration from PIA. A prior understanding of IB setup would help troubleshooting or any kind of configuraiton understanding in case something looks missing here.

Next step is to start the PUB/SUB App Server Processes... Once these server processes are up and running, reports would get displayed in Report manager - List/Explorer page.

Of course, basic IB setup is pre-requisite for the above activity to work. This includes Gateway configuration (PeopleTools -> Integration Broker -> Configuration -> Gateway), Gateway Setup Properties (PeopleTools -> Integration Broker -> Configuration -> Gateway -> Gateway Setup Properties), Quick Configuration (PeopleTools -> Integration Broker -> Configuration -> Quick Configuration) where you need to Gateway URLs and IB domains are active.

*** queries are always welcome.

COBOL - Configuring instance specific CBLBINs - Contd...

In continuation to previous blog: COBOL - Configuring instance specific CBLBINs, I would like to state an interesting problem I encountered with the configuration of instance specific CBLBINs. The problem was with a RemoteCall made to a COBOL program from an App Engine.

Payroll Interface app engine program PI_INRUN was going into "No Success" with message of COBOL program PIPINRUN abort. To dig out the problem further, I generated the log file by setting RCCBL Redirect=1 in psprcs.cfg. The file PIPINRUN_xxxxxx.err shows that the RemoteCall is looking for the desired cobol in wrong directory ($PS_HOME/cblbin) - not in the correct directory (which is the customized one) $PS_HOME/CBLBIN_INS.

The problem was because of one Remote Call paramter RCCBL PRDBIN which was missing from the psprcs.cfg (I am not sure, but it looks like that - the process scheduler config file in UNIX platform does not include this parameter by default). After entering this paramter (RCCBL PRDBIN=$PS_HOME/CBLBIN_INS) in Remote Call section of psprcs.cfg file and reconfiguring the process scheduler file - problem resolved. This parameter is used only when a Remote Call is made to a COBOL program from AE... for normal COBOL SQL programs, this parameter is not necessary.

Change Assistant

Download this document - (.doc) or (.pdf)

Change Assistant Introduction

Change Assistant (CA) was first released in PeopleTools 8.44. Change Assistant (CA) automates many task for applying any bundle, maintenance pack etc. Some benefits of using CA are:
- CA can find out bundles/MPs that have already been applied to a PeopleSoft Database
- CA can figure out Bundles/MPs that need to be applied
- CA can download new bundles/MPs
- CA can determine pre-requisites and post-requisites
- CA can determine the order in which new Bundles/MPs are applied
- CA can migrate bundle/MP project automatically
- CA can generate and execute DDL scripts
- CA can execute Data Mover Scripts
- CA can deploy files such as SQR, COBOL etc to file servers

Environment Management Framework (EMF)

PeopleSoft Environment Management (PSEM) Framework enables CA know about the PeopleSoft installation, configuration, and update information. It is used to obtain the configuration and setup information about PeopleSoft environments (i.e., the files servers, the web servers, the application servers, the process scheduler servers and the individual hosts/machines).

CA uses EMF to apply updates to PeopleSoft installation and configurations by helping in carrying out commands remotely on different machines.

EMF has three core elements:
- Environment Management Agent (PSEM Agent): A Java executable. Only one instance of the agent can run at a given time per physical machine. PSEM Agents are setup on each of the servers. Each PSEM Agent initiates communication to the hub (PSEMHUB) and is assigned a unique peer ID.
- Environment Management Hub (PSEMHUB): A web application that is installed at the time of PIA installation and resides at web server machine. It is started automatically at the time web server is booted up. This hub acts as a broker for all communication between peers. It gathers and reports on the environment information sent to it by PSEM Agents.
- Environment Management Viewer (PSEM Viewer): A command line tool that helps users view data that is retrieved from the PSEMHUB.
Before using Change Assistant (CA) for applying bundles/MPs, EMF should be configured and PSEMAgent should be started up on all the servers.

Change Assistant Validation

Make sure the HUB is up and running before starting EMAgents. Before starting the PSEMAgents – complete tasks below:
Web Server Specific: Delete the following directories:
$PS_HOME\webserv\peoplesoft\applications\peoplesoft\PSEMHUB\envmetadata\PersistentStorage
$PS_HOME\webserv\peoplesoft\applications\peoplesoft\PSEMHUB\envmetadata\scratchpad
$PS_HOME\webserv\peoplesoft\applications\peoplesoft\PSEMHUB\envmetadata\data\environment
$PS_HOME\webserv\peoplesoft\applications\peoplesoft\PSEMHUB\envmetadata\data\proxies
Except data.txt, delete other files from directory $PS_HOME\webserv\peoplesoft\applications\peoplesoft\PSEMHUB\envmetadata\data

Agent Specific: Delete the following directories on Linux machine:

$PS_HOME\PSEMAgent\envmetadata\data\ids
$PS_HOME\PSEMAgent\envmetadata\PersistentStorage
$PS_HOME\PSEMAgent\envmetadata\scratchpad
$PS_HOME\PSEMAgent\envmetadata\transactions (If it exists)
Except matcher.xml, delete other files from directory $PS_HOME\PSEMAgent\envmetadata\data

Viewer Specific: Delete the following directories on Linux and NT machines:
$PS_HOME\PSEMViewer\envmetadata\data\ids
$PS_HOME\PSEMViewer\envmetadata\PersistentStorage
$PS_HOME\PSEMViewer\envmetadata\scratchpad
$PS_HOME\PSEMViewer\envmetadata\transactions (If it exists)

Change Assistant Specific: Delete the following directories on the machine where Change Assistant being setup:
$PS_HOME\PSEMAgent\envmetadata\data\ids
$PS_HOME\PSEMAgent\envmetadata\PersistentStorage
$PS_HOME\PSEMAgent\envmetadata\scratchpad
$PS_HOME\PSEMAgent\envmetadata\transactions (If it exists)
Except matchers.xml, delete other files from directory $PS_HOME\PSEMAgent\envmetadata\data

Now start the PSEMAgent on each of the Application Server and Process Scheduler machines, which includes Linux as well as Windows machines.

Make sure EMAgents are running before using Change Assistant to validate the Environment Management Hub (PSEMHUB)

Change Assistant Setup
To start with, identify an environment that will act as a PSEMHUB.

Configure PSEHMHUB
To start with, identify an environment that will act as a PSEMHUB. In case of a single server configuration for PIA, the PSEMHUB is started whenever we start PIA… and uses the same http post as the PIA.
Let’s say if the PIA URL is: http://ws1_ip:9081/site/signon.html, the hubURL will be http://ws1_ip:9081/PSEMHUB/hub (Format of hubURL is: http://[server_name]:[port]/PSEMHub/hub )

To configure PSEMHUB:

- Go to below directory (of web server machine) $PS_HOME/webserv/DOMAIN_NAME/applications/peoplesoft/PSEMHUB/envmetadata/config

- Edit “configuration.properties” for hubURL, agentport (must be unique) and windowsdrivestocrawl or unixdrivestocrawl.
hubURL=http://ws1_1p:9081/PSEMHUB/hub
unixdrivestocrawl=/u02/pt848
or
windowsdrivestocrawl=D:\pt848

Configure PSEM Agent
To configure PSEM Agent:
- Go to $PS_HOME/PSEMAgent/envmetadata/config
- Edit “configuration.properties” for hubURL, agentport (must be unique) and windowsdrivestocrawl or unixdrivestocrawl.

Once PSEM Agent is configured, start the PSEM Agents in App Server machine, Process Scheduler Server machine, File Server machine, NT machine where CA is configured:
$PS_HOME/PSEMAgent/StartAgent.sh (in Unix) $PS_HOME/PSEMAgent/StartAgent.cmd (in Windows)

For the first time, start the PSEMAgent with recrawl command - so that it crawls the drives to identify the environment components (all servers):
$ $PS_HOME/PSEMAgent/StartAgent.sh recrawl (in Unix)
$PS_HOME/PSEMAgent/StartAgent.cmd recrawl (in Windows)

After recrawl is done, start PSEMAgent normally.
$ $PS_HOME/PSEMAgent/StartAgent.sh recrawl (in Unix)
$PS_HOME/PSEMAgent/StartAgent.cmd recrawl (in Windows)

Before doing so, you may want to modify the StartAgent.sh file in unix using nohup command - so that EM Agent keeps running even if we exit from unix box… To modify the StartAgent.sh, open it in vi editor and update the last line as:

nohup ../jre/bin/java com.peoplesoft.pt.environmentmanagement.agent.Agent $1 &

Save and exit.
Execute $./StartAgent.sh

Setup Change Assistance
Now, that we have done with the configuration of PSEMHUB and PSEM Agent – next step would be to setup Change Assistance.

Open the Change Assistance, and go to Tools -> Options:
- Select “Apply Application Update” as Change Assistant Mode
- Download directory is where we have downloaded the bundle or MP zip files
- Staging directory is the one which CA will use as a stage - it will extract zip files from Download directory to Staging Location and will use contents in this directory for processing
- Output directory is the one where CA will keep all the output files generated during implementation of a bundle or MP

Go to Tools -> Options -> Environment Management Tab:
- Server Host: enter the IP address of PSEMHUB machine
- Server Port: enter the Port Number at which PSEMHUB is configured
- Click Ping to check the connection
- Click View to see the Environment Management Hub Summary – it shows all the environments name and availability of their server components.
Go to Tools -> Scan Configuration:
Go to Tools -> validate:

Apply Change Packages (Bundles or MPs)

Go to Tools -> Apply Change Package:
- Next screen will show the installed environment found
- Select the target environment here
- Going ahead CA will ask for entering User ID (PeopleSoft User) and Access ID, Apply Directory (Download directory) etc.
- CA will show the list of all the change packages available at the above mentioned download directory as illustrated below
- Next, CA asks for the method to apply DB Build Scripts – I choose Manually option
- Next, CA shows the confirm selection screen where it summarizes to be applied MP or Bundle details
- Click Validate now
- Click Begin Apply

In Progress…

Next screen appears and I start applying the MP or Bundles now.

GUID

GUID uniquely identifies a database… PSOPTIONS tables stores value for GUID that is set the first time we start an Application Server… If our target database is refreshed by some source database, GUID would need to be reset… We would need to delete the existing value for GUID to blank in PSOPTIONS table – so that new value can be setup for the target database while booting the App Server for the first time.

Download this document - (.doc) or (.pdf)

Oracle Magazine

Many of you might find Oracle Magazine quite useful to keep you updated with the Oracle Database happenings... Here are the links:

http://www.oracle.com/oramag/index.html
http://www.oraclemagazine-digital.com/oraclemagazine/20090102/?sub_id=eKu28DLN3USD
http://www.oraclemagazine-digital.com/oraclemagazine/20081112/?sub_id=eKu28DLN3USD

Just for Information

I am redesigning my personal site www.rakeshparwal.com

Posting Issue - For Restarted AE, Dist Status is in ' Posting' forever

Note 1: AE Process restarted in Process Scheduler remains in Posting status forever. According to Oracle, it is a known issue in PT 8.48.08 and has been fixed in PT 8.48.11)

Note 2: Below is just an workaround to let other processes, which stuck up in posting status because of the re-started AE, go posted.

I recently came across a posting issue where lot of AE prcess were in Success/No Success runstatus but not getting posted... They were stuck up in POSTING dist status. Output were getting generated successfully in log_output directory, however, the process were in POSTING distribution status only (few of them were in the same status for 3-4 days)

PeopleTools 8.48:
One way to resolve such issue MIGHT be to upated the Distribution Status of such process instances from POSTING (7) to NOT POSTED (4) in PSPRCSQUE and PSPRCSRQST tables... And then post them again using RE-SEND option.

*** Find the prcs instances with distribution status of POSTING (7):

select PRCSINSTANCE, RUNSTATUS, DISTSTATUS from PSPRCSRQST where DISTSTATUS='7';

select PRCSINSTANCE, RUNSTATUS, DISTSTATUS from PSPRCSQUE where DISTSTATUS='7';

*** Update these process instances' dist status from POSTING(7) to NOT POSTED (4)...

-- update PSPRCSQUE set DISTSTATUS='4' where PRCSINSTANCE IN (prcsinst_1, prcsinst_2, prcsinst_3);

-- update PSPRCSRQST set DISTSTATUS='4' where PRCSINSTANCE IN (prcsinst_1, prcsinst_2, prcsinst_3);

update PSPRCSRQST set DISTSTATUS='4' where PRCSINSTANCE in (select PRCSINSTANCE from PSPRCSRQST where DISTSTATUS='7');

update PSPRCSQUE set DISTSTATUS='4' where PRCSINSTANCE in (select PRCSINSTANCE from PSPRCSQUE where DISTSTATUS='7');

*** Post them again using RE-SEND option.

*** Also make sure all the three tables PSPRCSRQST, PSPRCSQUE, PSPRCSPARMS are in synce:

select count(*) from PSPRCSRQST;

select count(*) from PSPRCSQUE;

select count(*) from PSPRCSPARMS;

*** Values of Distribution Status can be found by using below query:

SELECT FIELDNAME, XLATLONGNAME, FIELDVALUE FROM PSXLATITEM WHERE FIELDNAME = 'DISTSTATUS';

FIELDNAME XLATLONGNAME FIELDVALUE

------------------------------------ ------------------------------------------------------------ ----------

DISTSTATUS None 0

DISTSTATUS Scheduled 1

DISTSTATUS Processing 2

DISTSTATUS Generated 3

DISTSTATUS Unable to Post 4

DISTSTATUS Posted to Web 5

DISTSTATUS Delete 6

DISTSTATUS Posting 7

8 record(s) selected.