vax to ux conversion (was nonsense subject)

Roshan_Shah Roshan_Shah@Satyam.com
Thu, 15 May 2003 09:24:54 +0530


I totally agree with Terry's Message.

Although - I still can't understand that HP ("HP Invent") who now owns
Digital don't have inventive people to implement solutions on their Boxes.
In a procedural way the first step should be to 

a) Find a Solution yourself ( Experienced people won't ask Solutions here
;-) as they already know way to get things done )

b) If not, try and call Cognos Support ( Especially if you fall in the
umbrella of Big Company like HP - they may want you not to look stupid ;-) )

c) If don't find a solution there - then try other means.....

As far as Offshore work is concerned, it has nothing to do with purely cost
cutting, the trend is that "Hey - If you are a Doctor - Focus on Patient
Cure - Don't try and keep pace with IT else you will lose Focus".  Most
offshore work to India, Phillipines, Mexico is from Companies who want to
find a long term partner who can Keep them ahead in IT - but they start the
relationship first with giving applications that are tightly coupled and
difficult(Cost inefficient) to maintain. However, I am also aware of lots of
cutting edge product developments going on in India for prestigious
solutions.

Bottomline is - That most of the companies in India are process oriented(We
have largest no of SEI CMM 5 Companies here).. Although you will see people
posting stupid questions at first but everything goes documented - knowledge
gets built and then you see a real value being delivered.

Regards
Roshan Shah
"Opinions are of my own and not of my Employer"
-----Original Message-----
From: Terry Curran [mailto:terrycurran@onetel.net.uk]
Sent: Wednesday, May 14, 2003 11:49 PM
To: 'Edis, Robert'; 'Powerh-L (E-mail)'
Subject: RE: vax to ux conversion (was nonsense subject)



As far as I am aware the only safe way to transfer PH from VMS to Unix
(any flavour),
is to:

1) Create the PDL source on the vax - from within QSHOW.

2) Create PORTABLE subfiles of any data which is required on the Unix
box.

3) FTP the PDL source, and the Portsble subfiles (usually a .PSD and .PD
file) to the unix box.

4) Create a new Dictionary on the unix bos, from the PDL file using the
PDL compiler.

5) create empty data files using QUTIL.

6) Re-load the data files from the portable subfiles.

And hey presto, you have you VMS data on unix!

Most PH source files will compile successfully against the new
dictionary.

You will probably need to make changes to the data dictionary source
file. Unix does not support all the data types of VMS, and the file open
is different, but any competent PH programmer should be able to do this
- Cognos used to have a manual about making your code portable, but I am
not sure that you can still get it, it had general advice about source
files.

PS - I have transferred PH from DG/AOSVS -> DG/UX , DG/UX -> VAX/VMS,
VAX/VMS -> SCO/UX, and a few others.

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

This email is brought to you courtesy of 1 & 1, for more details please
visit the 
link below

               http://oneandone.co.uk/xml/init?k_id=5753616

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

= = = = = = = = = = = = = = = = = = = = = = = = = = = =
Mailing list: powerh-l@lists.swau.edu
Subscribe: "subscribe" in message body to powerh-l-request@lists.swau.edu
Unsubscribe: "unsubscribe <password>" in message body to
powerh-l-request@lists.swau.edu
http://lists.swau.edu/mailman/listinfo/powerh-l
This list is closed, thus to post to the list you must be a subscriber.
************************************************************************** 
This email (including any attachments) is intended for the sole use of the
intended recipient/s and may contain material that is CONFIDENTIAL AND
PRIVATE COMPANY INFORMATION. Any review or reliance by others or copying or
distribution or forwarding of any or all of the contents in this message is
STRICTLY PROHIBITED. If you are not the intended recipient, please contact
the sender by email and delete all copies; your cooperation in this regard
is appreciated.
**************************************************************************