Setting up a DSL

Discussion of any ITIL or related issues that don't fit well into any of the above.
Post Reply
User avatar
rosevidney
Newbie
Newbie
Posts: 1
Joined: Sun Aug 12, 2007 8:00 pm

Mon Aug 13, 2007 10:12 am



User avatar
Roger
Senior Itiler
Senior Itiler
Posts: 35
Joined: Sun Aug 01, 2004 8:00 pm

Tue Aug 28, 2007 12:07 pm

User avatar
Guerino1
ITIL Expert
ITIL Expert
Posts: 500
Joined: Sat Dec 31, 2005 7:00 pm
Location: New Jersey
Contact:

Fri Aug 31, 2007 8:34 am

User avatar
Mark_B
Newbie
Newbie
Posts: 1
Joined: Mon Aug 03, 2009 8:00 pm
Location: Darwin, Australia

Tue Sep 01, 2009 2:07 am

Hi all,
Is anyone able to give me an example to what extent you have populated the DML? I am scoping out what to include - there are the obvious items like Lisences and Application Software, but coming from a shop which is both Midrange and Mainframe would you include JCL and Source Code even though they are already under the control of a Library Manager (SCLM)?

Cheers,
Mark
User avatar
Diarmid
ITIL Expert
ITIL Expert
Posts: 1894
Joined: Mon Mar 03, 2008 7:00 pm
Location: Helensburgh

Tue Sep 01, 2009 4:26 am

Mark_B wrote:would you include JCL and Source Code even though they are already under the control of a Library Manager (SCLM)?
Not my subject really, but the answer has to be that you consider how to manage and control all software so that it is always in a known state, subject to security, regression and other requirements and available for examination, development, testing etc.

Whether you bring all aspects of control into one database or develop practical management interfaces between many, is a matter of practicality.

does SCLM meet all your requirements of control and management for the system level software? Can you interface it or integrate it with your DML? should you migrate it to your DML? Are their training issues as well as other practicalities to consider?

Only you can tell in the end.

See Roger's post earlier in this thread.
"Method goes far to prevent trouble in business: for it makes the task easy, hinders confusion, saves abundance of time, and instructs those that have business depending, both what to do and what to hope."
William Penn 1644-1718
User avatar
Guerino1
ITIL Expert
ITIL Expert
Posts: 500
Joined: Sat Dec 31, 2005 7:00 pm
Location: New Jersey
Contact:

Tue Sep 01, 2009 8:24 am

Mark_B wrote:Hi all,
Is anyone able to give me an example to what extent you have populated the DML? I am scoping out what to include - there are the obvious items like Lisences and Application Software, but coming from a shop which is both Midrange and Mainframe would you include JCL and Source Code even though they are already under the control of a Library Manager (SCLM)?

Cheers,
Mark
Hi Mark,

The goal is to ultimately get everything into your DSL. However, keep in mind that if your enterprise is large enough, you'll have multiple mirror DSLs to keep performance adequate for each region. This will then breed the issue of managing one DSL as the master for all your other DSLs, which will feed from it or synchronize with it.

So, yes, I would keep all software, of any form, in your DSL.

One of the many advantages is that once you're code is located in one place, you can do things like write search scripts or metrics gathering scripts that you can run against your single source for code.

FYI... it's very important that you create a solid logical structure within your DSL for organizing what you create, in a very repeatable way that scales across projects, organizations, locations and, ultimately, regions.

My Best,

Frank
User avatar
BorisBear
ITIL Expert
ITIL Expert
Posts: 403
Joined: Sun Mar 09, 2008 8:00 pm
Location: Sunderland

Tue Sep 01, 2009 6:06 pm

Roger wrote:Hi Rachel

I see that a few folks have looked at your question, but not replied... I guess the reason is that it's a tricky question...

Firstly, as you may be aware the DSL and DHS are replaced by the DML in v3.. !!!!

BUT I have a favorite saying that I like to use for all tough questions... it's my saying and when you read it you will agree with me...

It all depends !

There are no hard and fast rules about what a DSL should look like or contain.. the important point here is that the DSL is a CONCEPT, rather than an actual product. The primary consideration is that the information about what is stored in the DSL is held in the CMDB.

You will also have a physical and electronic storage area and you will have names on media that follow your release policy. You will not have archives of software in the DHS... they will live in a seperate area.

I have to take issue with you here......thats just one word away from being UKVIKING's catchphrase - plagiarism at it's worst.
User avatar
Diarmid
ITIL Expert
ITIL Expert
Posts: 1894
Joined: Mon Mar 03, 2008 7:00 pm
Location: Helensburgh

Wed Sep 02, 2009 10:01 am

BorisBear wrote:
Roger wrote:I have to take issue with you here......thats just one word away from being UKVIKING's catchphrase - plagiarism at it's worst.
Look at the date. We have to establish precedence before making a call. It might just be a misdemeanour.
"Method goes far to prevent trouble in business: for it makes the task easy, hinders confusion, saves abundance of time, and instructs those that have business depending, both what to do and what to hope."
William Penn 1644-1718
User avatar
UKVIKING
ITIL Expert
ITIL Expert
Posts: 3639
Joined: Fri Sep 15, 2006 8:00 pm
Location: London, UK

Wed Sep 02, 2009 10:15 am

I did not implement Intellectual Property on It depends !

1 - I feared the lawsuits about adult diapers


And i could not decide whether the phrase was

It depends
IT depends
it depends

because.. you know.. it depends
John Hardesty
ITSM Manager's Certificate (Red Badge)

Change Management is POWER & CONTROL. /....evil laughter
User avatar
Diarmid
ITIL Expert
ITIL Expert
Posts: 1894
Joined: Mon Mar 03, 2008 7:00 pm
Location: Helensburgh

Wed Sep 02, 2009 10:58 am

Admit it John. You have a dependency issue.

Hang on and see if we can help you sort it.
"Method goes far to prevent trouble in business: for it makes the task easy, hinders confusion, saves abundance of time, and instructs those that have business depending, both what to do and what to hope."
William Penn 1644-1718
Post Reply