DSXchange

kunal,
what is posted is the copybook layout and -9 shows that the usage is display for the field, IT DOES NOT ESSENTIALLY HAVE TO BE A FLATTENED FILE.
as i see no comp3 var in the layout it will be perfectlly fine and viewable using the vi and other tools on Unix/Linux.

ask your mq admin to setup the failover service with lets say a as primary and B as secondary.
then use the service name in your mq stage.
in this case the switch over will be transparent to the application and any connect/reconnect will automatically will be routed to the required server.

the problem with the copybook is that its denoting the number fields in the display format (for which the mainframe have defined the fields to be used for diaplay), and replacing the "-" with S and and decimal to implied decimal will import the cipybook correctly and will reference the dat...

The issue here is your job forking out many processes which delays the start of the the process and it gets termineted after waiting like 600 seconds. you got options as below. - brakdown the job and run them sequentially to fork out less processes. - run the jobs on single node and ramp down the co...

best thing is to determine size of the data sets that you want to pull if >1gigs then flatten data for packed fields (convert to ASCII from EBCDIC) on mainframe and then ftp/sftp over to the datastage. this will save you the processing time for conversion on datastage. another alternative approach i...

depends on requirement if for real time and your middle ware layer supports messaging best thing is MQ.

Thanks for the explanation!

I'm a newbie on datastage. I am currently trying to get data from a seq. flat file pass to the modify stage and output it into a dataset file. For some reason I can get it to run without warnings but you know how the links glow Blue then Green when it runs and completes. Well I only get that blue to...