Dear Folks,

    I was just reviewing an article I wrote in 1988 (a long time ago) that encapsulates and summarizes my original efforts to learn SMP/E.

    Many of us systems programmers don't have a chance to do system maintenance, leaving it to "the designated person (or people)". And also, when breaking in a new person, that person is often given the job of doing the SMP/E system maintenance.  In my experience, the first exposure to SMP/E is a daunting task.  And it is even somewhat forbidding (to learn SMP/E) for very experienced systems programmers also, who (somehow) never ever got exposed to it, in their own LONG experience.

    My personal feeling (in 1988, after five years as a sysprog) was that, with the PROPER TEACHING, I could have learned, in 3 weeks, what took me 4 years to learn.

    I didn't want that to happen to anybody else.

    So I wrote an article.  Very carefully.

    I just read it over, today.  That's why I'm writing this piece.

    IF ANYBODY FEELS THE NEED TO LEARN SMP/E, PLEASE GO TO FILE 014 OF THE CBT TAPE (www.cbttape.org), and READ THE MEMBER, SMPARTCL.

    Part of the problem in learning SMP/E, is that IBM does not tell you about its history, and where it came from.  In order to really understand SMP/E, you first must have a grasp of doing a SYSGEN, to create a new MVS system.  We don't do SYSGENs anymore, so this makes it hard to understand the foundation and structure and purpose and method of operation, of SMP/E.

    Nevertheless, in that article, I tried to recreate the history, the best I could.

    BOTTOM LINE.  If you want to train someone, or yourself, to do SMP/E, please first read this article - CBT File 014 - member SMPARTCL.  It is almost guaranteed to make the process simpler.

    Hope this helps.........

    All the best of everything to all of you.

Sincerely,     Sam



----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to