Profile Scripting Language - Revision history

Kevdev59: Added category link for the company that the article says maintains this language

2021-04-29T06:09:25Z

Added category link for the company that the article says maintains this language

← Previous revision		Revision as of 06:09, 29 April 2021
Line 49:		Line 49:
	{{Major programming languages}}		{{Major programming languages}}

			[[Category:FIS (company)\| ]]
	[[Category:MUMPS programming language family]]		[[Category:MUMPS programming language family]]
	[[Category:MUMPS implementations]]		[[Category:MUMPS implementations]]

BlackcurrantTea: /* See also */ rm links used in article; added one so the section wouldn't be empty

2019-09-15T00:22:42Z

See also: rm links used in article; added one so the section wouldn't be empty

← Previous revision		Revision as of 00:22, 15 September 2019
Line 36:		Line 36:

	== See also ==		== See also ==
	* [[~~MUMPS~~]]		* [[Financial technology]]
	* [[GT.M]]
	* [[FIS (company)\|Fidelity National Information Services]]

	==References==		==References==

BlackcurrantTea: /* Language concepts */ wording change for NPOV

2019-09-15T00:13:51Z

Language concepts: wording change for NPOV

← Previous revision		Revision as of 00:13, 15 September 2019
Line 25:		Line 25:
	PSL interprets legacy MUMPS code, though some legacy commands (such as GO, NEW and KILL) can be disabled or marked as deprecated (generating compiler warnings). Direct references to MUMPS globals can also be disabled or deprecated. Numerous PSL compiler directives (e.g., #IF/#ELSE, #ACCEPT) were also added to the PSL language, as were Java style blocks and comments, modern error handling semantics and white space. Two MUMPS language elements were eliminated initially (M-style blocks and goto label+offset) as they could not be supported within the PSL object scope handling.		PSL interprets legacy MUMPS code, though some legacy commands (such as GO, NEW and KILL) can be disabled or marked as deprecated (generating compiler warnings). Direct references to MUMPS globals can also be disabled or deprecated. Numerous PSL compiler directives (e.g., #IF/#ELSE, #ACCEPT) were also added to the PSL language, as were Java style blocks and comments, modern error handling semantics and white space. Two MUMPS language elements were eliminated initially (M-style blocks and goto label+offset) as they could not be supported within the PSL object scope handling.

	~~An interesting feature of~~ PSL is ~~the~~ ~~ability~~ to ~~define~~ ~~a Class~~ as either Intrinsic or Extrinsic. Extrinsic classes implement Class, Method and Instance variable definitions consistent with common OO languages, and are generated into compiled code (accessed at runtime). Intrinsic Classes and methods, on the other hand are implemented as extensions to the PSL compiler itself, and are executed at COMPILE time in order to generate runtime code. This feature can generate heavily optimized or specialized code depending on compile time or program conditions. This capability was considered to be critical to the ability to generate code that optimized both a MUMPS global database and multiple commercial RDMS's from the same PSL source.		PSL allows a Class to be defined as either Intrinsic or Extrinsic. Extrinsic classes implement Class, Method and Instance variable definitions consistent with common OO languages, and are generated into compiled code (accessed at runtime). Intrinsic Classes and methods, on the other hand are implemented as extensions to the PSL compiler itself, and are executed at COMPILE time in order to generate runtime code. This feature can generate heavily optimized or specialized code depending on compile time or program conditions. This capability was considered to be critical to the ability to generate code that optimized both a MUMPS global database and multiple commercial RDMS's from the same PSL source.

	== Releases ==		== Releases ==

BlackcurrantTea: rm citation needed tags: redundant with article tagged as unref

2019-09-15T00:10:41Z

rm citation needed tags: redundant with article tagged as unref

← Previous revision		Revision as of 00:10, 15 September 2019
Line 5:		Line 5:
	\| year = 1998		\| year = 1998
	\| designer = Frank Sanchez		\| designer = Frank Sanchez
	\| latest_release_version =		\| latest_release_version =
	\| latest_release_date =		\| latest_release_date =
	\| typing =		\| typing =
	\| influenced_by = [[MUMPS]]		\| influenced_by = [[MUMPS]]
	\| influenced =		\| influenced =
	\| operating_system = [[Cross-platform]]		\| operating_system = [[Cross-platform]]
	}}		}}
Line 16:		Line 16:

	== History ==		== History ==
	PSL is a language that implements [[Object-oriented programming\|object orientated]] concepts such as classes, methods, encapsulation, inheritance, and strong data typing as extensions to the MUMPS language. PSL was initially conceived in December 1998 by Frank Sanchez, then President of Sanchez Computer Associates, as a transformation tool that could [[reverse engineer]] a very large and complex banking application (Fidelity National Information Services 'Profile') which was written predominantly in MUMPS.~~{{citation-needed\|date=March 2016}}~~		PSL is a language that implements [[Object-oriented programming\|object orientated]] concepts such as classes, methods, encapsulation, inheritance, and strong data typing as extensions to the MUMPS language. PSL was initially conceived in December 1998 by Frank Sanchez, then President of Sanchez Computer Associates, as a transformation tool that could [[reverse engineer]] a very large and complex banking application (Fidelity National Information Services 'Profile') which was written predominantly in MUMPS.

	Frank Sanchez developed the original language semantics, syntax, parser, compiler and optimizer, database interface, schema binding, intrinsic classes and methods over the Christmas holiday in 1998 and early 1999.~~{{citation-needed\|date=March 2016}}~~ He was assisted in the development of the initial commercial releases (version 1 - 2) by the late Bob Chiang, the Head of Data-Qwik tool development at Sanchez, and Mark Spier, a Senior Software Developer with Sanchez at the time. Sanchez Computer Associates (SCAI) was acquired by Fidelity National Financial (FNF), now [[FIS (company)\|FIS]], in April 2004.~~{{citation-needed\|date=March 2016}}~~ In later versions the compiler has been maintained and significantly enhanced by Frans Witte, a Senior Technical Lead at FIS, and Dan Russell, formerly the Head of Technology Development at Sanchez and now a remote Senior Technical consultant to FIS. Frans and Dan have focused on implementing the database independent features of the language, and more recently the Java source target code.~~{{citation-needed\|date=March 2016}}~~		Frank Sanchez developed the original language semantics, syntax, parser, compiler and optimizer, database interface, schema binding, intrinsic classes and methods over the Christmas holiday in 1998 and early 1999. He was assisted in the development of the initial commercial releases (version 1 - 2) by the late Bob Chiang, the Head of Data-Qwik tool development at Sanchez, and Mark Spier, a Senior Software Developer with Sanchez at the time. Sanchez Computer Associates (SCAI) was acquired by Fidelity National Financial (FNF), now [[FIS (company)\|FIS]], in April 2004. In later versions the compiler has been maintained and significantly enhanced by Frans Witte, a Senior Technical Lead at FIS, and Dan Russell, formerly the Head of Technology Development at Sanchez and now a remote Senior Technical consultant to FIS. Frans and Dan have focused on implementing the database independent features of the language, and more recently the Java source target code.

	== Language concepts ==		== Language concepts ==
	The initial language concepts included the ability to bind the source code to a database schema which generates dynamic Data Access Classes (preempting similar persistent class generation in [[Java (programming language)\|Java]]) and database methods that could be code generated into either MUMPS globals or a commercial [[Relational database management system\|RDMS]]. The PSL Data Access Classes are identified in the source code as Record<classes>.		The initial language concepts included the ability to bind the source code to a database schema which generates dynamic Data Access Classes (preempting similar persistent class generation in [[Java (programming language)\|Java]]) and database methods that could be code generated into either MUMPS globals or a commercial [[Relational database management system\|RDMS]]. The PSL Data Access Classes are identified in the source code as Record<classes>.

	PSL interprets legacy MUMPS code, though some legacy commands (such as GO, NEW and KILL) can be disabled or marked as deprecated (generating compiler warnings). Direct references to MUMPS globals can also be disabled or deprecated. Numerous PSL compiler directives (e.g., #IF/#ELSE, #ACCEPT) were also added to the PSL language, as were Java style blocks and comments, modern error handling semantics and white space. Two MUMPS language elements were eliminated initially (M-style blocks and goto label+offset) as they could not be supported within the PSL object scope handling.		PSL interprets legacy MUMPS code, though some legacy commands (such as GO, NEW and KILL) can be disabled or marked as deprecated (generating compiler warnings). Direct references to MUMPS globals can also be disabled or deprecated. Numerous PSL compiler directives (e.g., #IF/#ELSE, #ACCEPT) were also added to the PSL language, as were Java style blocks and comments, modern error handling semantics and white space. Two MUMPS language elements were eliminated initially (M-style blocks and goto label+offset) as they could not be supported within the PSL object scope handling.

	An interesting feature of PSL is the ability to define a Class as either Intrinsic or Extrinsic. Extrinsic classes implement Class, Method and Instance variable definitions consistent with common OO languages, and are generated into compiled code (accessed at runtime). Intrinsic Classes and methods, on the other hand are implemented as extensions to the PSL compiler itself, and are executed at COMPILE time in order to generate runtime code. This feature can generate heavily optimized or specialized code depending on compile time or program conditions. This capability was considered to be critical to the ability to generate code that optimized both a MUMPS global database and multiple commercial RDMS's from the same PSL source.~~{{citation-needed\|date=March 2016}}~~		An interesting feature of PSL is the ability to define a Class as either Intrinsic or Extrinsic. Extrinsic classes implement Class, Method and Instance variable definitions consistent with common OO languages, and are generated into compiled code (accessed at runtime). Intrinsic Classes and methods, on the other hand are implemented as extensions to the PSL compiler itself, and are executed at COMPILE time in order to generate runtime code. This feature can generate heavily optimized or specialized code depending on compile time or program conditions. This capability was considered to be critical to the ability to generate code that optimized both a MUMPS global database and multiple commercial RDMS's from the same PSL source.

	== Releases ==		== Releases ==
	The initial release of PSL (originally called M++) was in the summer of 1999, as part of the Profile version 6.2.~~{{citation-needed\|date=March 2016}}~~ In that release, less than 5% of the MUMPS code was converted to PSL, though new development was predominantly in PSL source code and analysis for widespread reverse engineering was underway. The Profile application conversion from MUMPS to PSL was 100% completed in 2006, with the release of Profile version 7.0. Profile version 7.0 was also the first commercial version of the application that could be targeted to run on either a [[GT.M]] MUMPS database or an [[Oracle Database\|Oracle 9 database]], with GT.M MUMPS source code as the PSL target.		The initial release of PSL (originally called M++) was in the summer of 1999, as part of the Profile version 6.2. In that release, less than 5% of the MUMPS code was converted to PSL, though new development was predominantly in PSL source code and analysis for widespread reverse engineering was underway. The Profile application conversion from MUMPS to PSL was 100% completed in 2006, with the release of Profile version 7.0. Profile version 7.0 was also the first commercial version of the application that could be targeted to run on either a [[GT.M]] MUMPS database or an [[Oracle Database\|Oracle 9 database]], with GT.M MUMPS source code as the PSL target.

	Currently PSL is continuing to be actively enhanced to support [[IBM DB2]] as a target database and to optionally generate either GT.M MUMPS or Java target code from the same PSL source code.~~{{citation-needed\|date=March 2016}}~~ Furthermore, PSL is supported by a modern [[Eclipse (software)\|Eclipse]]-based development environment, with integrated schema and code management and numerous interactive plug-ins. Jim Joyce, a senior R&D Developer at FIS has been responsible for much of the IDE vision and development.~~{{citation-needed\|date=March 2016}}~~		Currently PSL is continuing to be actively enhanced to support [[IBM DB2]] as a target database and to optionally generate either GT.M MUMPS or Java target code from the same PSL source code. Furthermore, PSL is supported by a modern [[Eclipse (software)\|Eclipse]]-based development environment, with integrated schema and code management and numerous interactive plug-ins. Jim Joyce, a senior R&D Developer at FIS has been responsible for much of the IDE vision and development.

	== Uses ==		== Uses ==
	As of June, 2011, PSL remains the source code language for the FIS Profile banking system, deployed in 26 countries and over 200 institutions, including some of the world’s largest banks.~~{{citation-needed\|date=March 2016}}~~ While Java and commercial RDMS deployments are possible in the future, today 100% of the deployments are on the GT.M MUMPS target language and database, with the exception of a single Oracle DBMS deployment.~~{{citation-needed\|date=March 2016}}~~		As of June, 2011, PSL remains the source code language for the FIS Profile banking system, deployed in 26 countries and over 200 institutions, including some of the world’s largest banks. While Java and commercial RDMS deployments are possible in the future, today 100% of the deployments are on the GT.M MUMPS target language and database, with the exception of a single Oracle DBMS deployment.

	== See also ==		== See also ==

AutisticCatnip at 04:00, 14 June 2019

2019-06-14T04:00:48Z

← Previous revision		Revision as of 04:00, 14 June 2019
Line 13:		Line 13:
	}}		}}

	'''Profile Scripting Language''' ('''PSL''') is a superset of the [[MUMPS]] [[programming language]] that adds [[Object-oriented programming\|object-oriented language features]]. It is currently developed by [[FIS (company)\|Fidelity National Information Services (hereafter FIS)]].		'''Profile Scripting Language''' ('''PSL''') is a superset of the [[MUMPS]] [[programming language]] that adds [[Object-oriented programming\|object-oriented language features]]. It is currently developed by [[FIS (company)\|Fidelity National Information Services]] (hereafter FIS).

	== History ==		== History ==

Widefox: Added {{unreferenced}} tag to article (TW)

2017-11-03T13:04:41Z

Added {{unreferenced}} tag to article (TW)

← Previous revision		Revision as of 13:04, 3 November 2017
Line 1:		Line 1:
			{{unreferenced\|date=November 2017}}
	{{Infobox programming language		{{Infobox programming language
	\| name = Profile Scripting Language		\| name = Profile Scripting Language

Widefox: /* top */ bold alt article name per MOS

2017-11-03T13:03:24Z

top: bold alt article name per MOS

← Previous revision		Revision as of 13:03, 3 November 2017
Line 12:		Line 12:
	}}		}}

	'''Profile Scripting Language''' (PSL) is a superset of the [[MUMPS]] [[programming language]] that adds [[Object-oriented programming\|object-oriented language features]]. It is currently developed by [[FIS (company)\|Fidelity National Information Services (hereafter FIS)]].		'''Profile Scripting Language''' ('''PSL''') is a superset of the [[MUMPS]] [[programming language]] that adds [[Object-oriented programming\|object-oriented language features]]. It is currently developed by [[FIS (company)\|Fidelity National Information Services (hereafter FIS)]].

	== History ==		== History ==

Master Of Ninja at 08:37, 19 March 2016

2016-03-19T08:37:06Z

← Previous revision		Revision as of 08:37, 19 March 2016
Line 1:		Line 1:
			{{Infobox programming language
			\| name = Profile Scripting Language
			\| paradigm = [[Procedural programming\|Procedural]]
			\| year = 1998
			\| designer = Frank Sanchez
			\| latest_release_version =
			\| latest_release_date =
			\| typing =
			\| influenced_by = [[MUMPS]]
			\| influenced =
			\| operating_system = [[Cross-platform]]
			}}

	'''Profile Scripting Language''' (PSL) is a superset of the [[MUMPS]] [[programming language]] that adds [[Object-oriented programming\|object-oriented language features]]. It is currently developed by [[FIS (company)\|Fidelity National Information Services (hereafter FIS)]].		'''Profile Scripting Language''' (PSL) is a superset of the [[MUMPS]] [[programming language]] that adds [[Object-oriented programming\|object-oriented language features]]. It is currently developed by [[FIS (company)\|Fidelity National Information Services (hereafter FIS)]].

Line 4:		Line 17:
	PSL is a language that implements [[Object-oriented programming\|object orientated]] concepts such as classes, methods, encapsulation, inheritance, and strong data typing as extensions to the MUMPS language. PSL was initially conceived in December 1998 by Frank Sanchez, then President of Sanchez Computer Associates, as a transformation tool that could [[reverse engineer]] a very large and complex banking application (Fidelity National Information Services 'Profile') which was written predominantly in MUMPS.{{citation-needed\|date=March 2016}}		PSL is a language that implements [[Object-oriented programming\|object orientated]] concepts such as classes, methods, encapsulation, inheritance, and strong data typing as extensions to the MUMPS language. PSL was initially conceived in December 1998 by Frank Sanchez, then President of Sanchez Computer Associates, as a transformation tool that could [[reverse engineer]] a very large and complex banking application (Fidelity National Information Services 'Profile') which was written predominantly in MUMPS.{{citation-needed\|date=March 2016}}

	Frank Sanchez developed the original language semantics, syntax, parser, compiler and optimizer, database interface, schema binding, intrinsic classes and methods over the Christmas holiday in 1998 and early 1999. He was assisted in the development of the initial commercial releases (version 1 - 2) by the late Bob Chiang, the Head of Data-Qwik tool development at Sanchez, and Mark Spier, a Senior Software Developer with Sanchez at the time. Sanchez Computer Associates (SCAI) was acquired by Fidelity National Financial (FNF), now [[FIS (company)\|FIS]], in April 2004. In later versions the compiler has been maintained and significantly enhanced by Frans Witte, a Senior Technical Lead at FIS, and Dan Russell, formerly the Head of Technology Development at Sanchez and now a remote Senior Technical consultant to FIS. Frans and Dan have focused on implementing the database independent features of the language, and more recently the Java source target code.{{citation-needed\|date=March 2016}}		Frank Sanchez developed the original language semantics, syntax, parser, compiler and optimizer, database interface, schema binding, intrinsic classes and methods over the Christmas holiday in 1998 and early 1999.{{citation-needed\|date=March 2016}} He was assisted in the development of the initial commercial releases (version 1 - 2) by the late Bob Chiang, the Head of Data-Qwik tool development at Sanchez, and Mark Spier, a Senior Software Developer with Sanchez at the time. Sanchez Computer Associates (SCAI) was acquired by Fidelity National Financial (FNF), now [[FIS (company)\|FIS]], in April 2004.{{citation-needed\|date=March 2016}} In later versions the compiler has been maintained and significantly enhanced by Frans Witte, a Senior Technical Lead at FIS, and Dan Russell, formerly the Head of Technology Development at Sanchez and now a remote Senior Technical consultant to FIS. Frans and Dan have focused on implementing the database independent features of the language, and more recently the Java source target code.{{citation-needed\|date=March 2016}}

	== Language concepts ==		== Language concepts ==
Line 11:		Line 24:
	PSL interprets legacy MUMPS code, though some legacy commands (such as GO, NEW and KILL) can be disabled or marked as deprecated (generating compiler warnings). Direct references to MUMPS globals can also be disabled or deprecated. Numerous PSL compiler directives (e.g., #IF/#ELSE, #ACCEPT) were also added to the PSL language, as were Java style blocks and comments, modern error handling semantics and white space. Two MUMPS language elements were eliminated initially (M-style blocks and goto label+offset) as they could not be supported within the PSL object scope handling.		PSL interprets legacy MUMPS code, though some legacy commands (such as GO, NEW and KILL) can be disabled or marked as deprecated (generating compiler warnings). Direct references to MUMPS globals can also be disabled or deprecated. Numerous PSL compiler directives (e.g., #IF/#ELSE, #ACCEPT) were also added to the PSL language, as were Java style blocks and comments, modern error handling semantics and white space. Two MUMPS language elements were eliminated initially (M-style blocks and goto label+offset) as they could not be supported within the PSL object scope handling.

	An interesting feature of PSL is the ability to define a Class as either Intrinsic or Extrinsic. Extrinsic classes implement Class, Method and Instance variable definitions consistent with common OO languages, and are generated into compiled code (accessed at runtime). Intrinsic Classes and methods, on the other hand are implemented as extensions to the PSL compiler itself, and are executed at COMPILE time in order to generate runtime code. This feature can generate heavily optimized or specialized code depending on compile time or program conditions. This capability was considered to be critical to the ability to generate code that optimized both a MUMPS global database and multiple commercial RDMS's from the same PSL source.		An interesting feature of PSL is the ability to define a Class as either Intrinsic or Extrinsic. Extrinsic classes implement Class, Method and Instance variable definitions consistent with common OO languages, and are generated into compiled code (accessed at runtime). Intrinsic Classes and methods, on the other hand are implemented as extensions to the PSL compiler itself, and are executed at COMPILE time in order to generate runtime code. This feature can generate heavily optimized or specialized code depending on compile time or program conditions. This capability was considered to be critical to the ability to generate code that optimized both a MUMPS global database and multiple commercial RDMS's from the same PSL source.{{citation-needed\|date=March 2016}}

	== Releases ==		== Releases ==
	The initial release of PSL (originally called M++) was in the summer of 1999, as part of the Profile version 6.2.{{citation-needed\|date=March 2016}} In that release, less than 5% of the MUMPS code was converted to PSL, though new development was predominantly in PSL source code and analysis for widespread reverse engineering was underway. The Profile application conversion from MUMPS to PSL was 100% completed in 2006, with the release of Profile version 7.0. Profile version 7.0 was also the first commercial version of the application that could be targeted to run on either a [[GT.M]] MUMPS database or an [[Oracle Database\|Oracle 9 database]], with GT.M MUMPS source code as the PSL target.		The initial release of PSL (originally called M++) was in the summer of 1999, as part of the Profile version 6.2.{{citation-needed\|date=March 2016}} In that release, less than 5% of the MUMPS code was converted to PSL, though new development was predominantly in PSL source code and analysis for widespread reverse engineering was underway. The Profile application conversion from MUMPS to PSL was 100% completed in 2006, with the release of Profile version 7.0. Profile version 7.0 was also the first commercial version of the application that could be targeted to run on either a [[GT.M]] MUMPS database or an [[Oracle Database\|Oracle 9 database]], with GT.M MUMPS source code as the PSL target.
	Currently PSL is continuing to be actively enhanced to support [[IBM DB2]] as a target database and to optionally generate either GT.M MUMPS or Java target code from the same PSL source code.

	~~Also~~, PSL is supported by a modern [[Eclipse (software)\|Eclipse]]-based development environment, with integrated schema and code management and numerous interactive plug-ins. Jim Joyce, a senior R&D Developer at FIS has been responsible for much of the IDE vision and development.		Currently PSL is continuing to be actively enhanced to support [[IBM DB2]] as a target database and to optionally generate either GT.M MUMPS or Java target code from the same PSL source code.{{citation-needed\|date=March 2016}} Furthermore, PSL is supported by a modern [[Eclipse (software)\|Eclipse]]-based development environment, with integrated schema and code management and numerous interactive plug-ins. Jim Joyce, a senior R&D Developer at FIS has been responsible for much of the IDE vision and development.{{citation-needed\|date=March 2016}}

	== Uses ==		== Uses ==
	As of June, 2011, PSL remains the source code language for the FIS Profile banking system, deployed in 26 countries and over 200 institutions, including some of the world’s largest banks. While Java and commercial RDMS deployments are possible in the future, today 100% of the deployments are on the GT.M MUMPS target language and database, with the exception of a single Oracle DBMS deployment.		As of June, 2011, PSL remains the source code language for the FIS Profile banking system, deployed in 26 countries and over 200 institutions, including some of the world’s largest banks.{{citation-needed\|date=March 2016}} While Java and commercial RDMS deployments are possible in the future, today 100% of the deployments are on the GT.M MUMPS target language and database, with the exception of a single Oracle DBMS deployment.{{citation-needed\|date=March 2016}}

	== See also ==		== See also ==
Line 35:		Line 47:
	* [http://www.mumps.cz/gtm/misc/PROFILE_ScriptingLanguage/help/InteractiveSQL.html Interactive SQL Help]		* [http://www.mumps.cz/gtm/misc/PROFILE_ScriptingLanguage/help/InteractiveSQL.html Interactive SQL Help]
	* [http://www.mumps.cz/gtm/misc/PROFILE_ScriptingLanguage/help/ProfileWebTools.html Profile Web Tools Overview]		* [http://www.mumps.cz/gtm/misc/PROFILE_ScriptingLanguage/help/ProfileWebTools.html Profile Web Tools Overview]

			{{Major programming languages}}

	[[Category:MUMPS programming language family]]		[[Category:MUMPS programming language family]]
			[[Category:MUMPS implementations]]

AnomieBOT: Dating maintenance tags: {{Citation-needed}}

2016-03-18T12:15:45Z

Dating maintenance tags: {{Citation-needed}}

← Previous revision		Revision as of 12:15, 18 March 2016
Line 2:		Line 2:

	== History ==		== History ==
	PSL is a language that implements [[Object-oriented programming\|object orientated]] concepts such as classes, methods, encapsulation, inheritance, and strong data typing as extensions to the MUMPS language. PSL was initially conceived in December 1998 by Frank Sanchez, then President of Sanchez Computer Associates, as a transformation tool that could [[reverse engineer]] a very large and complex banking application (Fidelity National Information Services 'Profile') which was written predominantly in MUMPS.{{citation-needed\|March 2016}}		PSL is a language that implements [[Object-oriented programming\|object orientated]] concepts such as classes, methods, encapsulation, inheritance, and strong data typing as extensions to the MUMPS language. PSL was initially conceived in December 1998 by Frank Sanchez, then President of Sanchez Computer Associates, as a transformation tool that could [[reverse engineer]] a very large and complex banking application (Fidelity National Information Services 'Profile') which was written predominantly in MUMPS.{{citation-needed\|date=March 2016}}

	Frank Sanchez developed the original language semantics, syntax, parser, compiler and optimizer, database interface, schema binding, intrinsic classes and methods over the Christmas holiday in 1998 and early 1999. He was assisted in the development of the initial commercial releases (version 1 - 2) by the late Bob Chiang, the Head of Data-Qwik tool development at Sanchez, and Mark Spier, a Senior Software Developer with Sanchez at the time. Sanchez Computer Associates (SCAI) was acquired by Fidelity National Financial (FNF), now [[FIS (company)\|FIS]], in April 2004. In later versions the compiler has been maintained and significantly enhanced by Frans Witte, a Senior Technical Lead at FIS, and Dan Russell, formerly the Head of Technology Development at Sanchez and now a remote Senior Technical consultant to FIS. Frans and Dan have focused on implementing the database independent features of the language, and more recently the Java source target code.{{citation-needed\|March 2016}}		Frank Sanchez developed the original language semantics, syntax, parser, compiler and optimizer, database interface, schema binding, intrinsic classes and methods over the Christmas holiday in 1998 and early 1999. He was assisted in the development of the initial commercial releases (version 1 - 2) by the late Bob Chiang, the Head of Data-Qwik tool development at Sanchez, and Mark Spier, a Senior Software Developer with Sanchez at the time. Sanchez Computer Associates (SCAI) was acquired by Fidelity National Financial (FNF), now [[FIS (company)\|FIS]], in April 2004. In later versions the compiler has been maintained and significantly enhanced by Frans Witte, a Senior Technical Lead at FIS, and Dan Russell, formerly the Head of Technology Development at Sanchez and now a remote Senior Technical consultant to FIS. Frans and Dan have focused on implementing the database independent features of the language, and more recently the Java source target code.{{citation-needed\|date=March 2016}}

	== Language concepts ==		== Language concepts ==
Line 14:		Line 14:

	== Releases ==		== Releases ==
	The initial release of PSL (originally called M++) was in the summer of 1999, as part of the Profile version 6.2.{{citation-needed}} In that release, less than 5% of the MUMPS code was converted to PSL, though new development was predominantly in PSL source code and analysis for widespread reverse engineering was underway. The Profile application conversion from MUMPS to PSL was 100% completed in 2006, with the release of Profile version 7.0. Profile version 7.0 was also the first commercial version of the application that could be targeted to run on either a [[GT.M]] MUMPS database or an [[Oracle Database\|Oracle 9 database]], with GT.M MUMPS source code as the PSL target.		The initial release of PSL (originally called M++) was in the summer of 1999, as part of the Profile version 6.2.{{citation-needed\|date=March 2016}} In that release, less than 5% of the MUMPS code was converted to PSL, though new development was predominantly in PSL source code and analysis for widespread reverse engineering was underway. The Profile application conversion from MUMPS to PSL was 100% completed in 2006, with the release of Profile version 7.0. Profile version 7.0 was also the first commercial version of the application that could be targeted to run on either a [[GT.M]] MUMPS database or an [[Oracle Database\|Oracle 9 database]], with GT.M MUMPS source code as the PSL target.
	Currently PSL is continuing to be actively enhanced to support [[IBM DB2]] as a target database and to optionally generate either GT.M MUMPS or Java target code from the same PSL source code.		Currently PSL is continuing to be actively enhanced to support [[IBM DB2]] as a target database and to optionally generate either GT.M MUMPS or Java target code from the same PSL source code.

Master Of Ninja at 11:55, 18 March 2016

2016-03-18T11:55:36Z

← Previous revision		Revision as of 11:55, 18 March 2016
Line 1:		Line 1:
	'''Profile Scripting Language''' (PSL) is a superset of [[MUMPS]] that adds object-oriented language features.		'''Profile Scripting Language''' (PSL) is a superset of the [[MUMPS]] [[programming language]] that adds [[Object-oriented programming\|object-oriented language features]]. It is currently developed by [[FIS (company)\|Fidelity National Information Services (hereafter FIS)]].

	==History==		== History ==
	~~Profile Scripting Language (~~PSL) is a language that implements OO concepts such as classes, methods, encapsulation ~~and~~ inheritance (and strong data typing) as extensions to the MUMPS language. PSL was initially conceived in December 1998 by Frank Sanchez, then President of Sanchez Computer Associates, as a transformation tool that could 'reverse engineer' a very large and complex banking application (Profile) which was written predominantly in MUMPS. ~~(Sanchez Computer Associates (SCAI) was acquired by Fidelity National Financial (FNF), now [[FIS (company)~~\|~~FIS]],~~ ~~in April, 2004)~~		PSL is a language that implements [[Object-oriented programming\|object orientated]] concepts such as classes, methods, encapsulation, inheritance, and strong data typing as extensions to the MUMPS language. PSL was initially conceived in December 1998 by Frank Sanchez, then President of Sanchez Computer Associates, as a transformation tool that could [[reverse engineer]] a very large and complex banking application (Fidelity National Information Services 'Profile') which was written predominantly in MUMPS.{{citation-needed\|March 2016}}

		⚫	Frank Sanchez developed the original language semantics, syntax, parser, compiler and optimizer, database interface, schema binding, intrinsic classes and methods over the Christmas holiday in 1998 and early 1999. He was assisted in the development of the initial commercial releases (version 1 - 2) by the late Bob Chiang, the Head of Data-Qwik tool development at Sanchez, and Mark Spier, a Senior Software Developer with Sanchez at the time. Sanchez Computer Associates (SCAI) was acquired by Fidelity National Financial (FNF), now [[FIS (company)\|FIS]], in April 2004. In later versions the compiler has been maintained and significantly enhanced by Frans Witte, a Senior Technical Lead at FIS, and Dan Russell, formerly the Head of Technology Development at Sanchez and now a remote Senior Technical consultant to FIS. Frans and Dan have focused on implementing the database independent features of the language, and more recently the Java source target code.{{citation-needed\|March 2016}}

			== Language concepts ==
	The initial language concepts included the ability to bind the source code to a database schema which generates dynamic Data Access Classes (preempting similar persistent class generation in [[Java (programming language)\|Java]]) and database methods that could be code generated into either MUMPS globals or a commercial [[Relational database management system\|RDMS]]. The PSL Data Access Classes are identified in the source code as Record<classes>.		The initial language concepts included the ability to bind the source code to a database schema which generates dynamic Data Access Classes (preempting similar persistent class generation in [[Java (programming language)\|Java]]) and database methods that could be code generated into either MUMPS globals or a commercial [[Relational database management system\|RDMS]]. The PSL Data Access Classes are identified in the source code as Record<classes>.

Line 10:		Line 13:
	An interesting feature of PSL is the ability to define a Class as either Intrinsic or Extrinsic. Extrinsic classes implement Class, Method and Instance variable definitions consistent with common OO languages, and are generated into compiled code (accessed at runtime). Intrinsic Classes and methods, on the other hand are implemented as extensions to the PSL compiler itself, and are executed at COMPILE time in order to generate runtime code. This feature can generate heavily optimized or specialized code depending on compile time or program conditions. This capability was considered to be critical to the ability to generate code that optimized both a MUMPS global database and multiple commercial RDMS's from the same PSL source.		An interesting feature of PSL is the ability to define a Class as either Intrinsic or Extrinsic. Extrinsic classes implement Class, Method and Instance variable definitions consistent with common OO languages, and are generated into compiled code (accessed at runtime). Intrinsic Classes and methods, on the other hand are implemented as extensions to the PSL compiler itself, and are executed at COMPILE time in order to generate runtime code. This feature can generate heavily optimized or specialized code depending on compile time or program conditions. This capability was considered to be critical to the ability to generate code that optimized both a MUMPS global database and multiple commercial RDMS's from the same PSL source.

			== Releases ==
	The initial release of PSL (originally called M++) was in the summer of 1999, as part of the Profile version 6.2. In that release, less than 5% of the MUMPS code was converted to PSL, though new development was predominantly in PSL source code and analysis for widespread reverse engineering was underway. The Profile application conversion from MUMPS to PSL was 100% completed in 2006, with the release of Profile version 7.0. Profile version 7.0 was also the first commercial version of the application that could be targeted to run on either a [[GT.M]] MUMPS database or an [[Oracle Database\|Oracle 9 database]], with GT.M MUMPS source code as the PSL target.		The initial release of PSL (originally called M++) was in the summer of 1999, as part of the Profile version 6.2.{{citation-needed}} In that release, less than 5% of the MUMPS code was converted to PSL, though new development was predominantly in PSL source code and analysis for widespread reverse engineering was underway. The Profile application conversion from MUMPS to PSL was 100% completed in 2006, with the release of Profile version 7.0. Profile version 7.0 was also the first commercial version of the application that could be targeted to run on either a [[GT.M]] MUMPS database or an [[Oracle Database\|Oracle 9 database]], with GT.M MUMPS source code as the PSL target.
	Currently PSL is continuing to be actively enhanced to support [[IBM DB2]] as a target database and to optionally generate either GT.M MUMPS or Java target code from the same PSL source code.		Currently PSL is continuing to be actively enhanced to support [[IBM DB2]] as a target database and to optionally generate either GT.M MUMPS or Java target code from the same PSL source code.

⚫	Frank Sanchez developed the original language semantics, syntax, parser, compiler and optimizer, database interface, schema binding, intrinsic classes and methods over the Christmas holiday in 1998 and early 1999. He was assisted in the development of the initial commercial releases (version 1 - 2) by the late Bob Chiang, the Head of Data-Qwik tool development at Sanchez, and Mark Spier, a Senior Software Developer with Sanchez at the time. In later versions the compiler has been maintained and significantly enhanced by Frans Witte, a Senior Technical Lead at FIS, and Dan Russell, formerly the Head of Technology Development at Sanchez and now a remote Senior Technical consultant to FIS. Frans and Dan have focused on implementing the database independent features of the language, and more recently the Java source target code.

	Also, PSL is supported by a modern [[Eclipse (software)\|Eclipse]]-based development environment, with integrated schema and code management and numerous interactive plug-ins. Jim Joyce, a senior R&D Developer at FIS has been responsible for much of the IDE vision and development.		Also, PSL is supported by a modern [[Eclipse (software)\|Eclipse]]-based development environment, with integrated schema and code management and numerous interactive plug-ins. Jim Joyce, a senior R&D Developer at FIS has been responsible for much of the IDE vision and development.

			== Uses ==
	As of June, 2011, PSL remains the source code language for the FIS Profile banking system, deployed in 26 countries and over 200 institutions, including some of the world’s largest banks. While Java and commercial RDMS deployments are possible in the future, today 100% of the deployments are on the GT.M MUMPS target language and database, with the exception of a single Oracle DBMS deployment.		As of June, 2011, PSL remains the source code language for the FIS Profile banking system, deployed in 26 countries and over 200 institutions, including some of the world’s largest banks. While Java and commercial RDMS deployments are possible in the future, today 100% of the deployments are on the GT.M MUMPS target language and database, with the exception of a single Oracle DBMS deployment.

			== See also ==
			* [[MUMPS]]
			* [[GT.M]]
			* [[FIS (company)\|Fidelity National Information Services]]

	==References==		==References==