Architecture required for a .Net front end and mainframe backend.

Forum rules

Post a reply


This question is a means of preventing automated form submissions by spambots.
Smilies
:D :) ;) :( :o :shock: :? 8-) :rofl: :x :cry: :P :oops: :!: :twisted: :roll: :evil: :?: :idea: :arrow: :| :good: :mrgreen: :sorry: :unknown: :yes: :lol:
BBCode is ON
[img] is ON
[url] is ON
Smilies are ON
Topic review
   

Expand view Topic review: Architecture required for a .Net front end and mainframe backend.

Re: Architecture required for a .Net front end and mainframe backend.

by Robert Sample » Thu May 12, 2016 7:59 pm

.Net can run on Linux which means it can run directly on system z these days.  Using it as a front end, though, you could use ODBC or SOAP, depending on what the mainframe has installed.  This question is so broad, however, that it is very difficult to answer.  CICS has web services these days, so if the .Net application is putting together the right formatted data, it could go to CICS on the mainframe even.

Architecture required for a .Net front end and mainframe backend.

by ArchitectQues » Thu May 12, 2016 3:49 pm

What is the Architecture required for a .Net front end and mainframe backend?

This is an interview question. More I talked about it more less I'm telling I felt. Also I found that question was too over board.  But if this questionis asked to you, what would you answer?

Top