K v ^ } µ } v / D ] t ] v ^ ] Ç í - Zendrepos.zend.com › ibmiphp › webinar › Day 1.pdfK À À ] Á

Open Source on IBM iWebinar Series

Day 1ERWIN EARLEY ([email protected]), SR. SOLUTIONS CONSULTANT, PERFORCE, NOVEMBER 2019

2 | COMMON Webinar Series: Open Source on IBM i | November 2019 zend.com

zend.com2 | Zend by Perforce © 2019 Perforce Software, Inc.

Overview

• Open Source Solutions are a driving factor/influencer in much of IT today▪ The IBM i platform can now benefit from Open Source in significantly

expanded ways then ever seen before on the platform

• This workshop provides an overview of Open Source on the IBM iPlatform

• The workshop is designed to leverage both lecture (presentation) as well as provide hands-on (after-hours) opportunities.

2



• Day 1: Monday 18-November 2019▪ Introduction to Open Source on IBM I▪ Why is Open Source on IBM i Important▪ Understanding the PASE environment as the enabler of Open Source on IBM I▪ Getting Familiar with the PASE environment▪ After-Hours Lab: Getting Familiar with PASE

• Day 2: Wednesday 20-November-2019▪ Exploring containers on IBM i▪ Managing Open Source on IBM i▪ Exploring Open Source Programming Languages▪ After-Hours Lab: Containers & Setting up Development Environment

• Day 3: Friday 22-November-2019▪ Open Source Programming Languages Integration with Db2 and ILE▪ Looking at the IBM i variant of the LAMP stack▪ Deploying LAMP-based solutions▪ After-Hours Lab: Open Source Programming Languages▪ After-Hours Lab: Deploying LAMP applications

Workshop Agenda

IBM Systems Technical University © 3



Logistics

• Workshop scheduled to run from 11:00AM – 2:00PM (Central)▪ Monday / Wednesday / Friday

• Will break about 75 minutes into the session• Materials available on the workshop system:

▪ http://idevphp.idevcloud.com

• Hands-on exercises to be completed outside of the webinar presentation time



• Open Source Overview

• Introduction to Open Source on IBM i

• Why is Open Source on IBM i Important

• Understanding the PASE Environment as the enabler of Open Source on IBM i

• Getting Familiar with the PASE environment

• After-Hours Lab: Getting Familiar with PASE

Day 1 Agenda

IBM Systems Technical University © 5



Free OSS ?

• “Software that gives users rights to run, copy, distribute, change and improve it as they see it, without them asking permission from or make payments to any external group or person”.

Mitre FOSS report 2002



Free as in “Freedom”

• Freedom to study the code• Freedom to improve the program• Freedom to run the program anytime, for any purpose on any machine.• Freedom to redistribute.

Free Speech not Free Beer



Free OS Software

• Apache• BIND• Emacs• FreeBSD• Ghostscript• Jakarta• Jboss• LaTex

• Linux• MySQL• Open Office• Perl• Samba• Sendmail• Snort• Squid



Why OSS ?

• Customizable• Improvable• Redistributable.• Runs Everywhere, for everyone.• Transparency.• Free !!!



Surprising !!

• How can the technical work of dozens, or even hundreds, of developers be coordinated without the usual project management apparatus?

• How do useful, well-designed products emerge from the individual actions of widely-distributed developers, with minimal central planning and relatively impoverished communication?



The OSS Developer WAY !

• Discuss the “itch” with a few• Code Development starts• Create website and “announce”.• Community evolves• Functionalities added• Feedback and Communication flows



Basic Open Source Software Development Process

Assert Requirements-

Design

Develop OSS Code

Manage Configuration

Download and Install

End-Use

Read, Analyze and Redesign

OSS Community Development Process

Communicate Experience



Open Source Software ?

• Open source software is FreeOSS that uses any license approved by the Open Source Initiative (OSI) from their list of approved open source licenses

• www.opensource.org/licenses/



Understanding the Open Source Process and Distributions

• Contributors: Submit code changes to maintainers for consideration• Maintainers: Ownership (from a maintenance viewpoint) of a particular component

(application)▪ The maintainer is responsible for review of changes submitted by contributors,

incorporation of accepted changes into the component, and releases of an updated component (application)

14



End-User Influence on Open Source

• End-Users can report defects and request enhancements through the open source application’s defect tracking system▪ Typically ‘bugzilla’

• End-users have the “freedom” to review the open source, code their own changes, and submit them to the open source project maintainer.

15



Communication is Informal!!

• Community communications▪ Threaded discussion forums▪ Email (list servers)▪ Newsgroups▪ IRChat/Instant messages▪ Community digests (“Kernel Cousins”)



People involved



OSSD into commercial world

• IBM considers it important▪ Customers ask for it▪ Developing in open community leads to innovation▪ Develops open standards



Why is OSSD successful ?

• Collaboration is decentralized. Integration is controlled• Too many resources to fail• So many eyeballs looking at the code• Self-motivated , self-assigned programmers.• Large scale Peer Review• User Driven requirements



OSSD vs PSD: It differs a lot !

• Different Paradigms• Cathedral vs Bazaar• To name a few

▪ Assignment of work▪ Change Management▪ Testing & Bug Fixing



Assignment of work

• You assign (Baby Sitter)▪ Laggard▪ Sit inside the boundary

• I pick (Parent)▪ More responsibility▪ More care▪ Avenues for exploration▪ Quality product



Testing and Bug Fixing

• PS Industry spends 40% of time on testing and bug fixing.▪ White box testing ▪ Black box testing

• In OSSD it is a community process▪ Bugzilla▪ IssueTracker



Assessing Open Source Solutions

• Evaluation/assessment of any solution is imperative to the successful implementation of a quality solution

• Steps in the evaluation process are really no different from those you would use with closed source (or commercial) solutions, just the time spent differs▪ Step 1: Identify candidate applications that may meet the business

requirements▪ Step 2: Review existing reviews/evaluations of the application(s)▪ Step 3: Compare basic attributes of the application(s) with against specific

requirements▪ Step 4: Perform an in depth analysis of the top candidate applications

• While the evaluation steps for proprietary and open source applications are the same the source of information for the identification and review steps are quite different▪ Proprietary solutions tend to be identified by the commercial vendor▪ Typically, the vendor provides documentation and literature on their product(s)▪ In the Open Source space, target applications are identified through a variety of

mechanisms including search engines and well known open source repositories such as sourceforge.net and freshmeat.net

23



Open Source Evaluation

• Sources of information to assist with Identification and Review steps:▪ The Enterprise Open Source Directory (http://www.eosdirectory.com) provides an on-

line catalog of open source projects▪ The opensourceCMS site (php.opensource.com) has a ratings page that provides

customer ratings of popular CMS packages▪ Wikipedia has a list of free and open source applications by category

(http://en.wikipedia.org/wiki/List_of_free_and_open_source_software_packages)▪ The Free Software Foundation maintains a Free Software Directory

(http://directory.fsf.org/)▪ An Open Source Software Directory, compete with user ratings for the applications, is

also available (http://www.opensourcesofsoftwaredirectory.com)▪ The InsideCRM web site (http://www.insidecrm.com) provides a list of the top 10 CRM

packages. Rankings of CRM packages can also be found at the CRMSoftware360 website (http://www.crmsoftware360.com)

▪ The wiki rankings available on the web are somewhat dated; however, you might want to take a look at the Top 5 open source Wiki engines article on the Tech Corner web site (http://www.benh.org/techblog/)

▪ OSS Watch (http://www.oss.watch.ac.uk) can be a great resource for obtaining advice and guidance on the use, development and licensing of open source software applications

24



Open Source Evaluation

Factors to consider• Reputation: What is the application's reputation for performance and reliability

▪ Some of the sites on the previous slide provide information on what others have experienced with the application

▪ Reputation of an application is often directly related to its popularity− While it's hard to gauge the popularity of a particular open source application

there are some metrics that can be used to anecdotally determine the popularity such as download counters for the product as well as site counters for Internet based applications

• Ongoing effort: Is there an ongoing effort to continue development of the application including both defect resolution as well as incorporating enhancements and new functionality?▪ Places to look for this information include the application web site▪ Another good place to look would be the sourceforge web site

• Standards: Does the application adhere to a documented set of standards?▪ Is there a requirement for the solution to be able to integrate with other

applications?− What are the integration capabilities of the application under review?

25



Open Source Solutions Evaluation

Factors to Consider• Documentation: What level of documentation is available for the open source application?

▪ Popular open source applications like the SaMBa file server and Apache web server have a wealth of documentation available including both open source as well as commercial resources

▪ For less popular open source applications it is possible that documentation may lag release of product versions

• Versioning: When was the last stable version of the application released?▪ Ensure that there is an ongoing development effort for the application▪ Be aware that version numbers in open source don't necessarily follow the conventions of

commercial applications− As an example, often times when evaluating commercial applications customers will tend to

stay away from those applications whose version numbers end in a zero (0) as that represents the first release of a new version of the application

− This may not be the case in open source – where 1.0 usually represents the first release of a commercial application, version 0.1 may represent the first version of an open source application

− Keep in mind there is no “standard” for version numbers in the open source space.• Licensing: Review and understand the licensing aspects of the product and that it meets the

requirements▪ Not all open source licenses are created equal

26



Open Source Solutions Evaluations

• Review of application literature should provide information necessary for the comparison of functions provided to those required▪ Keep in mind – this comparison will only be as good as the initial definition of the

requirements to be satisfied• Functional review should result in a subset (typically one or two) candidate applications

migrating to the top of the “desired” list• Here's the fun part!! Establish a test environment and kick the tires of those

application(s) that you want to further review▪ Leverage the virtualization capabilities of the Power system to establish a Linux test

LPAR (or KVM guest, or even a Docker container) for further evaluation of the application(s)

• Once the application face-off is complete, put the winning application into production.

27



Overview

• 78% of business are now operating on open source software

• More than 50% find open source to be more secure than proprietary software Open Source Software has an inherent business value

• With open source as the foundation of a business an enterprise is able to remove barriers that encourage innovation and entrepreneurialism. All permissions required to deploy, run, migrate, collaborate, and innovate have been provided in advance



Open Source on IBM i: Timeline

1988 JTOpen

2002 Apache

2006 Zend PHP

2013 PowerRuby

2014 Node.JS

2015 Python

2016 Tools

2017 Nginx

2018 RPMs

5733-OPS



Open Source Solutions on IBM i

ApacheOpenSSLOpenSSHJTOpenetc

PythonNode.JSGitOrionetc.

XMLServiceLanguage ToolkitsIBM I Services (SQL)etc.

Many I OSS projectsActive collaborationBlogs, articlesetc.

Legacy Offerings 5733OPS Integration Community



Assimilation

Sustainable Revenue

Real Business Applications

Ecosystem & Documentation

Basic Infrastructure

First Stop – Basic Infrastructure

slice

PASE Languages

SSL, SSHcompilers




• The basic infrastructure of support has to be in place to allow us to build upon it with real-world solutions

• For IBM i, the basic infrastructure includes items such as:▪ SLIC▪ PASE▪ Programming Languages▪ Compilers▪ Protocol support – such as SSL and SSH



Assimilation

Sustainable Revenue




Next Stop – Ecosystem & Documentation

Integration pieces Workable examples

Language modules

GNU tools

API librariesFrameworks



XML Service / aka XML Toolkit

• Set of classes that access IBM i native artifacts▪ All program objects

− RPG, COBOL, CL, etc.

• Others▪ Command processor

Data Queues▪ Spooled File▪ More…

• Access naturally from PHP code.▪ No SPs required

• Easy to use



Two Parts

• XML Service▪ Developed by IBM and contributed to the community as open source▪ Made up of RPG, CL and DB2 stored procedures (SQL)

• Toolkit (the PHP side)▪ Series of classes that "wrap" the calls to the ILE Toolkit ▪ All PHP but Object Oriented (but easy to learn and use)▪ Zend built the PHP wrapper▪ No OO training required to use them

• Other open source languages have their own wrapper (toolkit)

http://yips.idevcloud.com/wiki/index.php/XMLService/XMLService



Capabilities/Benefits of ILE Access

• Leverage existing business logic – no need to re-write• Provide new interfaces for existing data objects and artifacts

Use Case: Need to convert an existing RPG application to run in web browsers.

Solution: When using PHP as the "vehicle" to "convert" the application it's unlikely that 100% of the application will have to be rewritten. With PHP, the existing RPG code can be encapsulated into smaller programs or service programs containing modules. The programs and modules can be easily called using the ILE Toolkit.

Use Case: Leverage complex pricing routine written in RPG in a new web presence

Solution: Extract code from existing application and create an API in RPG. The resulting API can then be called from the PHP script thereby leveraging the investment in the existing application while using PHP to concentrate on the user interaction portion of the desired solution.



DB2 Storage Engine for MySQL and MariaDB

• Supports open source applications (i.e., LAMP-based) while simplifying data management▪ Applications written to MySQL or MariaDB can store

their data in DB2 without any code change▪ One database to manage, backup, and protect▪ RPG applications, DB2 Web Query have access to

MySQL/MariaDB generated data.

• PHP, Apache, and MySQL/MariaDB enable 1000s

of applications on IBM I including:

– CRM, ecommerce, Portals, Wikis, blogs, etc

I

B

M

i

A

pache

M

ySQL

P

HP



Assimilation

Sustainable Revenue




Final Stop (for now) – Ecosystem & Documentation



IBM i – enabled for Open Source Solutions

• IBM i runs many of the industry standard technologies, such as PHP, Apache, and MySQL/MariaDB that enables web solutions like Jenkins and Wordpress to be run natively on the platform

• These applications can be easily deployed and leveraged



The Toolkits – integrating with IBM i

• Each Open Source Language has a toolkit that provides the ability to integrate the language with Db2 as well as ILE programs and artifacts.

• Db2 access provides the ability to execute SQL statements from the language against Db2.

Examples from Node.js, python, and PHP will be covered in the Open Source Programming Languages materials



Toolkit links

• Toolkits provide the ability to integrate with various features/functions/programs of IBM I

• Node.js toolkit: ▪ https://bitbucket.org/litmis/nodejs-itoolkit

• PHP Toolkit for IBM i:▪ http://yips.idevcloud.com/wiki/index.php/XMLSERVICE/Python▪ https://bitbucket.org/litmis/python-itoolkit

• Python itoolkit-lite▪ https://bitbucket.org/litmis/nodejs-itoolkit

• Ruby itoolkit▪ https://bitbucket.org/litmis/ruby-itoolkit

• Swift ▪ https://bitbucket.org/litmis/swift-itoolkit

• .NET▪ https://github.com/richardschoen/IbmiXmlserviceStd

NOTE: Documentation for Ruby, Swift, and .NET is not sufficient to complete the capability information provided on the following slides



Open Source Databases

• MariaDB – Major part of the LAMP-stack ecosystem▪ Includes a storage engine for access to Db2

• MongoDB – NoSQL Document store database• Redis – In-memory key/value store



Businesses are "dying" of thirst in an ocean of data"

1 in 2business leaders don’t

have access to data they need

83%of CIO’s cited BI and

analytics as part of their visionary plan

54%of companies use

analytics for competitive advantage

80%of the world’s

data today is unstructured

90% of the world’s

data was created in the last two years

20%is the amount of

available data traditional

systems leverages

Source: GigaOM, Software Group, IBM Institute for Business Value"



Background• Relational Database Management Systems (RDBMS) have been, and

continue to be, the primary method for storage of data• Open Source RDBMS offerings such as MySQL/MariaDB, and

PostgreSQL augment proprietary solutions such as DB2 and Oracle

• Popular web sites linking to smaller web sites can cause significant increases in traffic

• This is sometimes referred to as the 'Slashdot Effect'

• RDBMS tends to be geared to support OLTP. • Hooking these database to web-based applications can can cause

database content from hundreds of thousands of visitors in a short span of time

• Fronting the RDBMS with read-only cache, like memcached and Redis, can offload a considerable amount of the read traffic

• The growth of datasets has shown limitations in the RDBMS model



Background (continued)

• RDBMS were not intended/designed to be distributed• Attempting to scale up when the datasets become large causes

issues

• Limitations in scaling led technologists to look at multi-node database solutions

• This has become to be known as "scaling out" or "horizontal scaling"

• Different approaches to scaling include• Master-Slave• Sharding

• The best way to provide ACID and rich query model is to have the database on a single host

• There are limits to vertical scaling (although one could argue this point when it comes to IBM i)

• The CAPP theorem provides an alternative to ACID – more on this in a moment



NoSQL Defined• Originally stood for Not SQL

• Has come to be known as Not Only SQL

• Provides a class of non-relational data storage systems• Usually does not require a fixed table schema

• NoSQL databases do not use the concept of joins

• NoSQL relaxes one or more of the ACID properties [implements CAP, more on that in a moment]

• As a reminder: • Atomicity – each transaction is treated as a single unit which either

succeeds or fails completely• Consistency – a transaction can only bring the database from one

valid state to another• Isolation – ensures that concurrent transactions will leave the

database in the same state as if the transactions had been executed sequentially

• Durability – once a transaction has been committed it will remain committed



Document Database Example – What is MongoDB?

• Developed by in 2007 (based in New York). • Released as open source in 2009 under the GNU

Affero General Public License (AGPL) and Apache License (language drivers)

• Community free edition has been downloaded 30 million times 1

• NoSQL Database: Uses collections of documents instead of rows in a table.

• Written in C++, C and JavaScript• Dynamic schema design: Provides flexibility and

changes usually have minimal impact on code. Be agile.

1 https://techcrunch.com/2017/09/21/database-provider-mongodb-has-filed-to-go-public/



REDIS Overview• REDIS (Remote Dictionary Server) is an in-memory

data structure store that can be used as:• Database• Cache• Message Broker

• Has support for data structures such as:• Strings• Hashes• Lists• Sets• Sorted sets• Bitmaps• Hyperloglogs• Geospatial index



Use Cases

• A replacement for memcached

• A work-queue (sets & lists)

• Fast auto completion (persistent, queryable)

• Caching for Nginx via the Nginx HTTP Redis module

• Simple full-text search for multiple data stores redis-textsearch

Memcached is a general-purpose distributed memory caching system that is often used to speed up dynamic database-driven websites by caching data and objects in RAM



NoSQL in the IBM i ecosystem

• Cassandra is implemented via Java – as such it should work "out of the box"

• An AIX binary of Redis is available and has been used by a number of IBM i shops

• MongoDB enables numerous Node.JS applications so just like MySQL was ported to enable PHP-based applications (i.e., LAMP) it is likely that MongoDB will be ported to IBM I to enable Node.JS-based applications

• Remember that 80% of new data being generated is unstructured – new solutions to support the explosion of non-structure data needs/will be available on IBM i



ActiveMQ

• Message-oriented middleware• Apache project

▪ http://acivemq.apace.org/

• Apache license• Goal:

▪ Standards-based, message-oriented application integration across many languages and platforms



git

• Git provides Source Code Control / Version Control• Version control is a system that keeps records of all changes• Enables collaborative development• Enables auditing – knowing who did what and when• Facilitates rolling back changes to a previous state



Orion

• Some refer to Orion as an IDE on the cloud

• Browser-based open tools integration platform▪ Focused on developing for the web, on the web▪ Focus on web developers working on client-side JavaScript, CSS, and HTML

• Orion is a set of server and client-side components/code that when brought together make up an extensible browser-based development platform.

• Supports integration with Git, as well as shell access, site definition, dealing with various tasks, etc.



Nginx

• Pronounced at "Engine X"

• Open Source web and reverse proxy server

• High-performance HTTP, HTTPS, SMTP, iMAP, and POP3 server

• Supports load balancing and HTTP caching

• Architecture is asynchronous and event-driven



Nginx – Why Use It

• Lightweight and small memory footprint• Uses predictable memory under load• Provides high level of concurrency• Serves static content quickly• Handles connections asynchronously• Uses single thread



Comprehensive support solutions



TSS Support Offering

With a continuously evolving product list, TSS can support virtually the entire ecosystemSupport Products List – March 2018



More than just Break / Fix



Significant Supported OSS Solutions for IBM i• Git• Jenkins• rsync• Node.js• Apache Tomcat • WordPress• Python• Redis• Ansible

• For more resources, see http://ibm.biz/ibmi-oss-support



Is Open Source Strategic

"Development on IBM i continues to evolve, and open source development tools are common."

https://www.helpsystems.com/resources/guides/ibm-i-marketplace-survey-results



Open Source Solutions address many of the top concerns of IBM i shops




Core Infrastructure Initiative (CII)

A project managed by The Linux Foundation whose intent is to enable technology companies, stake holders, and developers to collaboratively identify, fund and improve the security of critical open source project.

Members of CII include

https://www.coreinfrastructure.org/



Open Source vs. Closed Source (proprietary)Open Source Closed Source/Proprietary

Malicious people have easy/ready access to source code

Malicious people can't see source code but can still reverse engineer

Funded by a community, coalition, or foundation

Funded by the owner

Zero to many developers Traditional development team

Code quality can be verified – peer review

Code quality assured by owner –typically internal review

Anyone can fix defects Owner fixes defects

Community maintains update schedule Owner maintains update

Testing community driven including "bounty hunters"

Owner-staffed test team

Generally quick to adopt new protocols.[OpenSSL support for TLSv1.3 since April 5][NSS support since before then]

Requirements submitted to product owner for new protocols.







Better availability through load balancing

NGINX is an open source package that supports functions such as web serving, reverse proxy, caching, load balancing, media streaming and more.

And YES, NGINX runs on IBM i!







IBM addresses modernization with every new version

• FastCGI• Allows fast connection from HTTP

server to backend PASE environment

• Instrumental in PHP performance

• ILE Object Toolkit• Allows connects from various

languages (PHP, Python, perl, ruby, etc) to ILE objects and IBM I native artifacts

• SQL Connector• Easily integrated way to transfer

data to and from Db2 for i leveraging SQL.



The Web is driven by Open Source

• Languages• PHP• Python• Ruby• Javascript

• Packages• JSON / XML• Swagger API

framework• SOAP libraries• Web frameworks

• Application Framework/Servers

– Apache Tomcat / TomEE

– Jboss EAP

– Greenfish

– Rails

– Epxress.js

– Salis.js

– Django

– Bottle

– Flask

• HTTP Servers

– Apache HTTP Server

– nginx

– Eclipse Jetty







Open Source Skills in High Demand• Open Source skills are the skills being sought after

• Universities and trade schools offer wide-range of open-source related courses

https://www.tiobe.com/tiobe-index/



Skills

• Acquisition• Easy to find developers to write

applications on your IBM I

• Utilization• Open Source

technologies/languages provide opportunity for current staff to learn new skills







Analytics/Business Intelligence• Many packages available in open source communities

• Often these packages can run on the IBM i, or integrate with IBM i with the help of open source technologies



Integration with other data sources• Most new/modern languages have OSS packages to interact

with social media

• Various OSS packages facilitate the consumption of XML or JSON feeds

• Many databases have open source clients available

• Open Source DBMS enable new applications• MySQL/MariaDB• PostgeSQL

• Open Source DBMS enable new streams of data• MongoDB• REDIS

Another area where open source on IBM i will facilitate handling the growth in data source and data feeds is the implementation of NoSQL databases as a method of aggregating data stream input into DB2.







Open Source Free?

• Sort of, but… consider• The "glue" required to integrate various technologies together

• OSS licensing – not all are created equal

• Staying current• Getting support



Open Source Meets Business Needs

• latest security protocols, cipher suites, etc

• Secure software trusted by virtually the entire industry

Security

• Application-level availability solutions, including pm2, nginx, gunicorn, etc.

High Availability




• Solutions for web development• Easy ways to achieve SOA, web

services, microservices• New languages• Unprecedented capabilities (IoT,

quantum computing, 3d visualization, etc etc etc)

Modernizing Applications

• Well-known languages and frameworks• Industry-standard tools (a

“normalization” of the application developer's environment)

IBM i Skills




• Several business intelligence and reporting tools (BIRT)

• A convenient conduit to cloud-based solutions like Watson

• Machine learning• Connectivity to social media or other

databases

Data Growth/Analytics/BI

• Sometimes…. FREE!• Often…. not free, but cost-competitive• Affordable support options

Reduction of IT Spending



Greatest cybersecurity challenges



Greatest cybersecurity challenges (top five)

• Lack of security knowledge and skills

• Threats are changing constantly

• Balancing Security Controls and Business Efficiency

• Evolving technology (mobile, IoT, cloud, etc)

• Lack of budget for security projects



Greatest cybersecurity challenges (top five)

• Lack of security knowledge and skills▪ OSS brings “googlable” solutions

• Threats are changing constantly▪ OSS constantly evolves as new threats arise

• Balancing Security Controls and Business Efficiency▪ OSS brings cost-effectiveness with industry-standard technology

• Evolving technology (mobile, IoT, cloud, etc)▪ OSS thrives in all these areas and solutions already exist

• Lack of budget for security projects▪ OSS has multimillion-dollar investments from many companies



Evolution of the Platform

• What’s Came Before – A few highlights▪ CISC to RISC▪ POWER Convergence▪ LPARs (VMs)▪ Db2 Enhancements

• The Evolution Continues▪ PHP for Application Modernization▪ 3rd Party Solutions (like phpGrid) for rapid modernization▪ Open Source Support delivering languages and solutions



https://spectrum.ieee.org/static/interactive-the-top-programming-languages-2018

Popular Languages on IBM i



Machine Learning enabled on IBM i

• RPM enablement• Python enablement• BLAS enablement• Db2 connection

• Most famous ML packages available▪ Numpy, Pandas for data processing▪ Scipy, Scikit Learn for ML and scientific analysis▪ ipython, interactive python language support▪ nltk, natural language toolkit for natural language ML process.▪ matplotlib, jupyter notebook for visual/interactive ML/data analysis



Demo-scikit-learn

• Multi-label classification.▪ Each sample has 20 features ▪ We try to use Support Vector Machine (SVM) based on the chosen features(2

features selected) by canonical correlation analysis (CCA) or principal component analysis (PCA), which make it easier for us to show on plot.

refs: https://scikit-learn.org/stable/auto_examples/plot_multilabel.html#sphx-glr-auto-examples-plot-multilabel-py



Demo-scikit-learn

• visualizing the stock market structure.▪ try to get the stock open/close prices for some companies as training data.▪ Using the GraphLassoCV to train the data.▪ Using the trained model’s covariance matrix to calculate the classes and labels.▪ Giving out the clusters output based on assinged labels.▪ Meanwhile, visualizing the results into a 2d plane.

refs: https://scikit-learn.org/stable/auto_examples/applications/plot_stock_market.html#sphx-glr-auto-examples-applications-plot-stock-market-py



Demo-scikit-learn



ActiveMQ

• Open source message broker (Java-based)• Supported protocols:

▪ OpenWire▪ STOMP▪ MQTT▪ AMQP▪ REST▪ WebSockets



.NET Available on IBM i!!

• Mono has been ported to IBM i!!

• Community Effort

• Available via third-party RPM repository

https://bitbucket.org/ibmi/opensource/src/master/docs/yum/3RD_PARTY_REPOS.md



DevOps-enabling tools with IBM i

• git• Ansible• Jenkins• Jira• BarryCI• Nagios (monitoring)



Git• Open Source distributed version control system• Source control for virtually any language• Powerful and flexible• Can have hooks to perform custom actions when new code is

integrated• Already in use in the IBM i community



Ansible with IBM i

• Ansible comes with integration for RPM (yum) management!!▪ (after all, Ansible, RPMs, and Yum are all RedHat technology!)

• https://docs.ansible.com/ansible/latest/modules/yum_module.html



Ansible+Jenkins in production use

• Node.js CI system▪ Ansible used to provision test environments and systems▪ Jenkins oversees tests, provides dashboards, etc



PASE - Overview

• By 2000, AIX and OS/400 were able to run on the same POWER processors.

• This created the possibility for executables which are MI-based and AIX-based to run on the same hardware in the same partition

• PASE makes it possible for those binaries to run in the same process• PASE is not a release of AIX but rather a set of AIX libraries

▪ Fitted to talk to SLIC rather than directly to the AIX kernel

• PASE gets the memory from the same SLIC teraspace pools used by ILE▪ For program run stack, heap, and shared memory▪ PASE can ONLY see memory that PASE acquired through its own syscall APIs



What PASE isn’t!

• PASE is not an emulated environment

• PASE is not a separate environment from IBM I▪ As an example the same Integrated File System (IFS) is accessed from PASE as

from any other part of IBM I▪ A further example, applications/tools/programs started in PASE can access Db2

data and ILE programs/artifacts



PASE Architecture

• PASE provides a set of AIX shared libraries that run directly on the POWER processor▪ Applications in PASE enjoy the same performance as applications running an

AIX partition

• A syscall interface provides ability for applications in PASE to call ILE applications and access Db2 resident data



PASE Applications IBM i Applications

IBM i Operating System (above TIMI)

Technology Independent Machine Interface

PASE Shared Libraries

syscall

POWER Hardware

SLIC(IBM i below TIMI)



IBM Speak

• PASE supports the application binary interface (ABI) of AIX and provides a broad subset of the support provided by AIX shared libraries, shells, and utilities.

• PASE also supports the direct processing of IBM PowerPC machine instructions, so it does not have the drawbacks of an environment that only emulates the machine instructions

• PASE applications:▪ Can be written in C, C++, Fortran, or PowerPC assembler▪ Use the same binary executable format as AIX PowerPC applications▪ Run in an IBM i job▪ Use IBM i system functions, such as file systems, security, and sockets

https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_74/rzalf/rzalfwhatispase.htm



IBM Speak

• PASE run-time runs on the Licensed Internal Code (LIC) kernel on the IBM i operating system.

• The system provides integration of many common IBM i functions across PASE and other runtime environments including Integrated Language Environment (ILE) and Java.

• PASE implements a broad subset of AIX system calls• System support for PASE enforces system security and integrity by

controlling what memory a PASE program can access and restricting theprogram to use only unprivileged machine instructions

https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_74/rzalf/rzalfwhatispase.htm



Integration – Getting from Here to There (and back again)

• Call PASE from IBM iQSH CMD('ls /home/Erwin')

• Call IBM i from PASEsystem "WRKOBJLCK OBJ(MYFILE) OBJTYPE(*FILE)"

• More robust integrations such as accessing Db2 and ILE programs from open source languages is possible – more on that later



• To be effective with working in the PASE environment requires a certain knowledge and/or affinity with working in *NIX-line environments

• Shell concepts is a good skill to acquire.

Working in PASE

• What is a Shell?

• Working with the shell

• Working in PASE

Mini Agenda



Agenda

• Setting up the OSS ecosystem support in PASE• Setting up the user environment• Defining a container (chroot)• Installing OSS packages• Python – an example• Node.js - an example



Setting up the OSS Ecosystem in PASE



RPM Pile Overview

• IBM has released an RPM pile that provides the packages from 5733-OPS (plus a lot more) in a RPM-based repository

• This allows for installation of open source packages in a Linux-like fashion with PASE

• Currently available on IBM i 7.2 and newer• The RPM pile contains many packages including:

▪ Node.js version 8▪ Python 3.6▪ The 'less' utility▪ git▪ The 'updated' and 'locate' utilities▪ GCC 6.3.0 and other development tools▪ GNU Nano▪ Others…

The RPMs are not AIX RPMs. They are IBM i RPMs shipping IBM i Software. Built on IBM i, for IBM i.

https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/IBM%20i%20Technology%20Updates/page/Open%20Source%20RPM's



Installing the RPM/YUM support

• Step 1: Download the bootstrap file to your PC:ftp://public.dhe.ibm.com/software/ibmi/products/pase/rpms/bootstrap.sql

• Step 2: Run the SQL script against the system you want to install RPMs on



RPM pile bootstrap

create or replace table qtemp.ftpcmd(cmd char(240));create or replace table qtemp.ftplog(line char(240));--delete from qtemp.ftpcmd with nc;--delete from qtemp.ftplog with nc;insert into qtemp.ftpcmd(CMD) values

('anonymous [email protected]'),('namefmt 1'),('lcd /tmp'),('cd /software/ibmi/products/pase/rpms'),('bin'),('get README.md (replace'),('get bootstrap.tar.Z (replace'),('get bootstrap.sh (replace')with nc

;



RPM pile bootstrap (continued)

CL:OVRDBF FILE(INPUT) TOFILE(QTEMP/FTPCMD) MBR(*FIRST) OVRSCOPE(*JOB);CL:OVRDBF FILE(OUTPUT) TOFILE(QTEMP/FTPLOG) MBR(*FIRST) OVRSCOPE(*JOB);CL:FTP RMTSYS('public.dhe.ibm.com');CL:QSH CMD('touch -C 819 /tmp/bootstrap.log; /QOpenSys/usr/bin/ksh /tmp/bootstrap.sh > /tmp/bootstrap.log 2>&1');

Selectcase when (message_tokens = X'00000000')then 'Bootstrapping successful! Review /tmp/README.md for more info'else 'Bootstrapping failed. Consult /tmp/bootstrap.log for more info'end as resultfrom table(qsys2.joblog_info('*')) xwhere message_id = 'QSH0005'order by message_timestamp descfetch first 1 rows only;



RPM/YUM installation steps continued

• Step 3: Once the installation of the bootstrap is complete, start a terminal session▪ This can be done via 5250 command 'call qcmd'▪ Better yet, an SSH session can be established to the system

• Step 4: Modify the PATH to include the bin directory for the packages installed by the bootstrap

PATH=/QOpenSys/pkgs/bin:$PATHexport PATH



Useful Commands

Command Description

bash A shell typically available on Linux systems. Features include command/file completion, and command recall.

gcc GNU c Compiler

rpm Used to install/manage packages built using the Redhat Package Manager.

yum Yellowdog Updated, Modified – a wrapper around RPM that uses package repositories to simplify package installation and dependency resolution



Setting up the User Environment



Creating the User Environment

• A number of steps should be accomplished to create the user environment

• Step 1: Create the user's home directorymkdir /home/<username>

• Step 2: Create a .profile in the user's home directory. The .profile is used to define the shell environment, including environment variables, scripts to execute, and other commands. The .profileis used to store pre-defined settings when a shell program starts

PATH=/QOpenSys/pkgs/bin:$PATHexport PATH

bash

– The first two lines update the path statement to include the location of the programs installed both by the bootstrap as well as subsequent 'yum install' commands

– The third line causes the bash shell to be executed

• NOTE: by default a PASE terminal session starts the 'ksh' shell



Changing the default shell

• The default shell in the PASE environment is ksh (a favorite in the AIX space)

• A better alternative to ksh is bash – a favorite in the Linux space especially for it’s features like command recall (up-arrow) and file-name completion (tab).

• The ‘qsys2.set_pase_shell_info’ function can be used to change the default shell either for an individual user or for all users:

call qsys2.set_pase_shell_info(‘*DEFAULT’, ‘/QOpenSys/pkgs/bin/bash’);

• To check the default shell:

select authorization_name, pase_shell_pathfrom qsys2.user_infowhere pase_shell_path is not null;



Repository Definition

• The RPM packages reside in a repository that is publicly accessible

• The definition of the repository is located in the /QOpenSys/etc/yum/repos.d directory▪ The repository file for the IBM RPM pile is ibm.repo

[ibm]name=ibmbaseurl=http://public.dhe.ibm.com/software/ibmi/products/pase/rpms/repoenabled=1gpgcheck=0

Note: it is possible to use a local repository by downloading the files from the indicated FTP site and then uploading them to a directory on the system. The 'baseurl' would change to indicate 'file' and the path to the directory of RPMs.

Additional note: ACS has support for cloning the repository to a local server.



Environment VariablesOverview

• An environment variable is a name/value pair that can affect running process within a computing environment

• The current environment can be output with the 'env' command

# envSSH_CONNECTION=10.165.1.229 49163 10.68.240.201 22TZ=<CST>6<CDT>,M4.1.0,M10.5.0USER=qsecofrPWD=/HOME/QSECOFRHOME=/HOME/QSECOFRSSH_CLIENT=10.165.1.229 49163 22SSH_TTY=/dev/pts/0MAIL=/var/spool/mail/qsecofrTERM=xterm-256colorSHELL=/QOpenSys/usr/bin/bshSHLVL=1LOGNAME=qsecofrPATH=/QOpenSys/pkgs/bin:/QOpenSys/usr/bin:/usr/ccs/bin:/QOpenSys/usr/bin/X11:/usr/sbin:.:/usr/binLOGIN=qsecofr_=/QOpenSys/usr/bin/envOLDPWD=/QOpenSys/etc/yum/repos.d



Environment VariablesVariables of Note

Variable Description

USER Current user logged into system and using the current shell

PWD The current working directory. This is the 'focus' of any command run on the system

HOME The user's home directory. This is the directory that is typically used for storage of configuration files that affect a user's login environment as well as shell characteristics. NOTE: This directory does not exist by default in the IBM i environment – more on that in a moment.

SHELL The current shell. The environment supports multiple shells including bash and ksh

LOGNAME The login name of the user

OLDPWD The previous (n-1) working directory



What is a Shell?• The command line used on “Unix™” systems (as well as Unix-like systems) as

well as PASE

• Like CL it can be used interactively, or run as a program

• Like CL most commands are actually programs that get called

– There are some “built in” commands

• Unlike CL there are a number of varieties of shell

– sh bourne shell

– csh c shell

– ksh korn shell

– bash bourne again shell

– qsh Q shell

• There are some similarities and some differences

• Most of the discussion here is not operating system specific

– Will work on AIX, Linux, QSH in OS/400, other nasty Unix variants, etc



Why do we care about the shell?

• All system configuration operations can be done through the shell – often

more quickly then through a GUI

• Shell scripts can automate routine tasks such as backups, scheduled emails,

etc.

• GUI can be used for a great amount of admin activities

– However, the shell tends to be a comfort zone providing ability to fix

things in case something goes wrong



Different Types of Shells• A number of shells are available each providing function/usability customized to a

particular type of user:

• Popular shells include:

– BASH (Bourne Again Shell)

– PDKsh (Public Domain Korn Shell)

– csh (C shell)

– mc (Midnight Commander)

– QSHELL (PASE shell)

– ksh (Korn shell, default on AIX)

• Difference tends to be in scripting capabilities and user interface

– Items such as command recall and file name completion are typically different



Starting with bash

• bash stands for Bourne Again Shell

– Developed by Brian Fox in 1987

– One of the most popular shells available in Linux

• Bash incorporates features of the Korn and C shell (ksh and csh)

• Bash configuration files:

/bin/bash – Bash executable

/etc/profile – System wide initialization file for login shells

~/.bash_profile – Personal initialization file for login shells

~/.bashrc – Personal per-interactive-shell startup file

~/.bash_logout – Login shell clean file that executes when shell exits

Available in PASE!



A little more on BASH• Default Linux shell

• This can be changed in a variety of ways• /etc/profile – login shell• $HOME/.profile

• As we saw earlier, can be set as the default shell for PASE

• Very powerful as a command line shell• Recall previous commands• Command and file completion with the <TAB> key

• Many programming features• Loops and conditionals



Shell Environment• The shell is an environment where commands can be entered and the

Operations system can respond to them

• A key concept to the environment is environment variables

– There are a large number of environment variables

– HISTFILE: points to file containing the shell history, defaults to

~/.bash_history

– HISTFILESIZE: how man last commands you wish to have in history

– HOME: points to your home directory

– PATH: set of directories to search when trying to execute a command

– PS1: Prompt variable

– USER: usernameNOTE: All of these environment variables are available when running bash in the PASE environment.



Exploring the shell (command history/recall)

• The shell is the command-interpreter and as such there are a number of features that make it easier to work in and traverse the environment

• The shell keeps a history of previous commands that have been executed. The 'history' command can be used to display a list of those commands:

-bash-4.4# history1 pwd2 ls -l

• NOTES:

– The commands are shown preceded with a number. Any command in the history can be re-executed simply by entering ! Followed by the number from the command history list

– Previously executed command can be recalled through use of the up-arrow key. This allows you to scroll through previously executed commands.



Exploring the shell (file-name completion)

• A powerful feature of the bash shell is file-name completion• File-name completion s accomplished by pressing the <TAB>

key after entering a portion of a file-name.▪ At this point the shell will complete as much of the name as possible

while remaining unique▪ If there are multiple names that match what has been entered then

pressing the <TAB> key twice will show those matches.

type ls /QOPress <Tab>

Notice that the shell completes /QOpenSys/

Press <TAB> twice

Notice that the shell provides a list of items under /QOpenSys/



Shell metacharactersSymbol Meaning

> Output redirection

>> Output redirection (append)

< Input redirection

* File substitution wildcard; zero or more characters

? File substitution wildcard; one character

[ ] File substitution wildcard; any character between brackets

`cmd` Command substitution

$(cmd) Command substitution

| The pipe (connect output of command on right to input on command on left)

; Command Sequence

|| OR conditional execution

&& AND conditional execution



Shell metacharacters (continued)

Symbol Meaning

( ) Group commands

& Run command in the background

# Comment

$ Expand the value of a variable

\ Prevent or escape interpretation of the next character

<< Input redirection

" $val " Literal with variable substitution

' $val ' Literal without variable substitution



Why are metacharacters important

• The shell has two primary responsibilities• Walk the command-line looking for tokens• Cause a command string to be sent to the kernel

• Tokens are identified by white-space

• The metacharacters are considered tokens

ls –l /home/erwin > /tmp/listing



Useful Shell Constructs

• Arrow Up & Down: Scroll through recent commands used

• &&: command is only executed if preceding command was successful:

command1 && command2

• alias: sets a command alias or prints defined aliases

alias wrklnk=ls

• bg[jobid]: Resumes the suspended job in the background

• cd: changes current directory to directory indicated

cd /home



Useful Shell Constructs (continued)• echo: Outputs the arguments

echo "hello world"

• find [path][expression]: searches the directory indicating looking for files that match expression:

find / -name passwd –print

• pwd – Prints the absolute pathname of the current working directory

• unalias – Removes an alias

• history – displays command history with line numbers

• umask – User file creation mask

• logout: exits the shell environment

• exit [n]: exits shell environment with exit status n



"bash"ing PASE – yes I went there ;-) • The bash shell is available for PASE

• It is part of the RPM pile

• Step 1: Install the RPM pile bootstrap

• Step 2: Install bashyum install bash



Input and Output• *nix programs start with three open files

– Input (called stdin) (#0)

– Output (called stdout) (#1)

– Error output (called stderr) (#2)

• Our shell program uses the "echo" command to write to stdout

• We can redirect the output to go to a file by using ">"

ls –l > output.txt

This will take the output of the "ls –l" command and write it into a file called "output.txt"

STDOUT (1)program

STDIN (0)

STDERR (2)

STDIN (0)



Input and Output

• You can also specify which output goes to a file

ls –l 1> output.txtthis is the same as before.

• Redirecting only error output

grep fred * 2> grep.err

this will redirect only the error output to the file grep.err



Input and Output

• Use the "<" operator to redirect input– Equivalent to typing at the keyboard

• For example

sed "s/erwin/Erwin/g" < my.txt

This runs the command "sed" (an editor) changing "erwin" to "Erwin" and taking its input from a file called "my.txt"

• Input and output

sed "s/erwin/Erwin/g" < my.txt > my2.txt



Common *nix commands• Unix is built around the idea of lots of little programs that all do one thing well

– ls lists files

– sed an editor

– grep a searcher

– cat a file outputer

– find a file locator

– sort sorts files

– tr translates characters

– ps list processes

– seq print a sequence of numbers

– … a thousand others

• Help for all these is in the “man” (for “manual”) command

– e.g. man sed

• Shell programs generally involve stringing lots of these together

– Which leads us to “pipes”

All of these are available in the IFS and can be run from an IBM i shell (i.e., qsh, ssh session)

Many available on PASE and more coming!

Not currently available in PASE



Pipes• Standard output (STDOUT) of one command/program is used as

the standard input (STDIN) for the next command/program

ps –x | grep java

• List processes, search for any involving java

• Only the 'STDOUT' from the last command is actually output to the

screen (unless re-directed)

– NOTE: Any output to STDERR by the commands will be

output to the screen – again unless re-directed.

STDIN (0)STDOUT (1)

NOTE: pipes are not limited to two commands… any number of pipes can be used to build a pipeline:cmd1 | cmd2 | cmd3 | …. | cmdx



SAMBA Deeper Dive



What is SaMBa

Briefly…•SaMBa is an Open

Source file server and client compatible with Microsoft Networking, that comes with many current distributions of Linux

•SaMBa is the UNIX implementation of the SMB protocol (CIFS)

SaMBa is…• Free

• Popular

• Licensed under the GPL

• Andrew Tridgell’s brainchild

• Highly configurable

• Constantly being enhanced

• Vendor independent



Protocol

SMB – CIFS • Server Message Block

▪ This protocol defines ways for a client to request files from a server▪ The SMB protocol was created by IBM in 1985.

− It was named the IBM PC Network SMB Protocol▪ There are numerous SMB dialects

− The dialect defines the level of Windows integration that the client making the file/print request supports

− SAMBA 3.0 implements the NT-level dialect which allows for Domain Controller support and integration with Active Directory

− SaMBa 4.0 implements the AD-level dialect which allows for Active Directory Services

• Common Internet File System (CIFS)▪ CIFS is an extension of Microsoft’s SMB protocol. It is optimized to run over the

Internet or Intranets and implements file-level security mechanisms▪ CIFS allows users to share documents over the Internet in the same way they

share documents when running peer networking services on their internal SMB networks.



SAMBA Capabilities

• Allows users to share files• Allows users to share printers• Allows users to time sync their machines off of the SAMBA server• Allows the system administrator to perform remote password

administration• A NetBIOS name server which, among other things, gives browsing support.

▪ SAMBA can be the master browser on your LAN if you wish• A tar extension to the client for backup of PCs• Ability to integrate with existing Active Directory domains• Ability to provide Active Directory services (new with version 4.0 of SAMBA)



SAMBA Configuration – The Basics



Components of SMB

Component Description

smbd A daemon process that provides file and print services to SMB clients.

nmbd A daemon process that provides NetBIOS name service and browsing support

winbindd A daemon process used for integrating authentication and the user database into UNIX

• SAMBA provides a number of programs and utilities that implements the SMB protocol support as well as providing Active Directory services.



Programs & Tools

Program / Tool

Description

smbclient The smbclient program implements a simple ftp-like client. Used to access SMB shares

testparm Simple syntax checker for Samba’s configuration file.

smbstatus Provides access to information about the current connections to the smbd daemon.

nmblookup Allows NetBIOS name queries to make from a UNIX host.

smbpasswd Tool for changing LanMan and Windows NT password hashes on SAMBA servers.

smbcacls A tool to set ACL’s on remote CIFS servers

smbtree Text-based network neighborhood tool

smbtar Make backups of data on CIFS/SMB servers

smbspool A helper utility for printing on printers connected to CIFS servers



Programs & Tools

Program / Tool

Description / Usage

smbcontrol Change the behavior of running smbd, nmbd and winbindd daemons

rpcclient Used to execute RPC commands on remote CIFS servers

pdbedit Used to maintain the local user database on a samba server

findsmb Used to find SMB servers on the local network

swat Web-based interface for configuring SAMBA

wbinfo Retrieves and stores information related to winbind

profiles Command-line utility that can be used to replace all occurrences of a certain SID with another SID

ntlm_auth Helper-utility for external programs waiting to do NTLM-authentication

smbcquoatas Used to set remote QUOTA’s on server with NTFS 5.



SAMBA Configuration – The Basics

• Configuration is broken down into sections• Sections, introduced by [sectionName]

Basic Sections include[global]

• Specifies information such as workgroup, password checking, etc

• Settings apply to all shares

[homes]

• Can be used to share users home directories

[printers]

• Used to specify printers to share

Share Section

• Settings apply to this share



SAMBA – Defining Shares

• Sharing of file resources via SAMBA is supported at the directory level

– It is not possible to share individual files

• A “file share” is denoted in the SAMBA configuration file with the “share name” in brackets

• Guest support for file shares is supported – this share allows users who do not have accounts on the system to access the file share

• File shares can be hidden such that it is available but not included in the browse (windows network neighborhood) list

• ‘public = yes’ is the same as ‘guest ok = yes’– No password is required to

connect to the service

[public]available = yespath = /publicpublic = yesguest only = nowritable = yesbrowseable = yes

NOTE: On IBM i, SaMBa shares are defined in /opt/samba/lib/smb.conf



Sharing Users Home Directories

[homes]path = /home/%ubrowseable = nowritable = yes

• The %u is a variable substitution that is replaced with the name of the user that connected to the share.

• The ‘browseable = no’ line prevents the users’ home directory from being displayed as a share in the share list.

• The ‘writable = yes’ line ensures that Samba will allow the user to write into his/her own directory (assuming they have the necessary Linux file permissions)



SAMBA Installation

• The SAMBA that is currently available in the PASE environment is actually an AIX build.

• Documentation on the installation of SAMBA can be found at:▪ http://www-01.ibm.com/support/docview.wss?uid=nas8N1020089

• Step 1: Extract the SAMBA package (commands are run from the PASE environment)

mkdir sambacd sambajar xvf /QIBM/ProdData/OS/Samba.zip

$ mkdir sambacd sambajar xvf /QIBM/ProdData/OS/Samba.zipinflated: README.txtinflated: rpm_setup.shinflated: samba-3.6.25a-1.aix7.1.ppc.rpminflated: samba-3.6.25a.tar.gzinflated: samba_setup.sh



SAMBA Installation

• Step 2: The installation of SaMBa utilizes the rpm and wget utilities. Ensure that these are installed:

which rpmwhich wget

$ which rpm/QOpenSys/pkgs/bin/rpmwhich wgetno wget in /QOpenSys/pkgs/bin /QOpenSys/usr/bin /usr/ccs/bin /QOpenSys/usr/bin/X11 /usr/sbin . /usr/bin

• Step 3: If either of the packages are not available, install it with the yum command:

– yum install wget



SAMBA Installation

$ yum install wgetibm | 1.5 kB 00:00:00Setting up Install ProcessResolving Dependencies--> Running transaction check---> Package wget.ppc64 0:1.17.1-1 will be installed--> Finished Dependency Resolution

Dependencies Resolved

============================================================================================================Package Arch Version Repository Size

============================================================================================================Installing:wget ppc64 1.17.1-1 ibm 808 k

Transaction Summary============================================================================================================Install 1 Package

Total download size: 808 kInstalled size: 3.0 MIs this ok [y/N]: yDownloading Packages:wget-1.17.1-1.ibmi7.1.ppc64.rpm | 808 kB 00:00:00Running Transaction CheckRunning Transaction TestTransaction Test SucceededRunning Transaction

Installing : wget-1.17.1-1.ppc64 1/1

Installed:wget.ppc64 0:1.17.1-1

Complete!



SAMBA Installation

• Step 4: Run the installer:▪ chmod 755 samba_setup.sh▪ ./samba_setup.sh install

• Step 5: SAMBA and NetServer cannot both be running at the same time. Execute the following commands (from a 5250 session) to end NetServer▪ CRTUSRPRF NOBODY▪ ENDTCPSVR *NETSVR

• Step 6: From a PASE terminal session start the SaMBa daemon process▪ smbd &



Git"A 'git' is a cranky old man"

Linus Torvalds – creator of git



Overview

• Created by Linux Torvalds in 2005▪ Came out of the Linux development community▪ Designed for version control of the Linux kernel

• Goals of git▪ Speed▪ Support for non-linear development (thousands of parallel branches▪ Fully distributed▪ Able to handle large projects efficiently



Checking for / Installing git

• The which command can be used to see if git is installed▪ which git

• The yum install command can be used to install git▪ yum install git



Centralized vs. Distributed Version Control Systems

• Centralized VCS like Subversion, a central server repository (repo) holds the "official copy" of the code▪ The server maintains the sole

version history of the repo

• "checkouts" of the code are made to a local copy▪ Local modifications are made▪ Changes are not versioned

• When complete, the code is "checked in" back to the server▪ The checkin increments the repo's

version

• Distributed VCS like git doesn't support "checkout" from a local repo

– Code is "clone"d and changes are "pull"ed

• The local repo is a complete copy of everything on the remote server

– Local copy is "just as good" as the remove server copy

• Many options are local

– Check in/out from local repo

– Commit changes to local repo

– Local repo keeps version history

• When ready changes can be "pushed" back to the server

Centralized VCS Distributed VCS



Local git areas

• In a local copy on git, files can be:▪ In the local repo (committed)▪ Checked out and modified, but

not yet committed (working copy)

▪ In-between, in a "staging" area − Staged files are ready to be

committed− A commit saves a snapshot of all

staged states.



Initial git configuration

• Set the name and email for git to use when commits are made:▪ git config --global user.name "Erwin Earley"▪ git config --global user.email [email protected]

• Set the editor used for writing commit messages (default is vim)▪ git config --global core.editor nano

• Review the settings:▪ git config --list

# git config --listuser.name=Erwin [email protected]=nano



Cloning a git repo (local git repo)

• Creating a local git repository in the current directory▪ git init

− The above creates a .git directory in your current directory

− Files can then be committed in that directory into the repo

▪ To stage all changes in a file (or directory) for the next commit:

git add filename▪ Commit the staged changes using the –m argument as

the commit messagegit commit –m "commit message"

# cd python-scripts/bash-4.4# git initInitialized empty Git repository in /home/QSECOFR/python-scripts/.git/bash-4.4# git add *.pybash-4.4# git commit -m "initial commit"[master (root-commit) 4263c42] initial commit14 files changed, 167 insertions(+)create mode 100644 Ex01hello.pycreate mode 100644 Ex02Indent.pycreate mode 100644 Ex04Strings.pycreate mode 100644 Ex05Lists.pycreate mode 100644 Ex06tuples.pycreate mode 100644 Ex07Dictionary.pycreate mode 100644 Ex10ifs.pycreate mode 100644 Ex11Fors.pycreate mode 100644 Ex12While.pycreate mode 100644 Ex15Functions.pycreate mode 100644 Ex16Functions2.pycreate mode 100644 Ex17Functions3.pycreate mode 100644 datatype.pycreate mode 100644 variables.py



Cloning a git repo (remote repo)

• To clone a remote repository to the local directory▪ git clone url localDirectory

− Ex: git clone https://github.com/zendtech/ibmiToolkit toolkit

The above will create the specified directory (toolkit) that will contain a working copy of the files from the repo (https://github.com/zendtech/ibmiToolkit) as well as a .git directory that will be used to hold the staging area as well as the local repository.



git commandsCommand Description

git clone url [dir]

Copy a git repository so files can be added to it

git add file Adds file contents to the staging area

git commit Records a snapshot of the staging area

git status View the status of files in the working directory and staging area

git diff Shows the diff of what is staged and what is modified but unstaged

git pull Fetch from a remote repo and try to merge into the current branch

git push Push new branches and data to a remote repository

Good git cheatsheethttps://www.atlassian.com/git/tutorials/atlassian-git-cheatsheet



• An ssh client is needed to access the lab environment (5250 should not be used)▪ PuTTY is the typical client for Windows (ssh web browser from google could

also be used)▪ MAC has ssh built in▪ NOTE: ssh should be used in favor of QSH or CALL QP2TERM

• A token is provided with connection details including credentials

• If you run into problems/questions with the lab contact the instructor at [email protected]

Hands-on Exericse - Overview

160



COMMON Open Source on IBM i – common99

• System idevphp.idevcloud.com (port 22 – ssh)• User Name/Team common99• Password labpass• Port 10801

Questions/problems with hands-on exercises:

Send mail to [email protected]

Latest version of presentations and hands-on exercises available at:

http://idevphp.idevcloud.com/webinar



• Establish connection to the lab environment• Get familiar with working at the CLI of the PASE environment• Work with text editors

▪ nano▪ joe

• Explore file system concepts▪ Permissions▪ Ownership▪ Links

• Work with processes

Lab Outline

162



• Exploring Containers on IBM i

• Managing Open Source on IBM i

• Exploring Open Source Programming Languages

Day 2 Preview

163



• /QOpenSys is where all of the open source files reside

The /QOpeSys directory structure

164

/

QOpenSys

etcbin pkgslib tmpsbin varusr

homedev lib sbin tmp usr var

container

QOpenSysdevbin home lib sbin tmp usr var

etcbin pkgslib tmpsbin varusr



The /QOpeSys directory structure

165

Directory Contents

bin Commands

dev Device Files

etc Configuration files

home User Home Directories

lib Libraries

pkgs Package files / commands

sbin Privileged commands

tmp Temporary files

usr Utilities & Applications

var Variable files

Documents

K v ^ } µ } v / D ] t ] v ^ ] Ç í - Zendrepos.zend.com › ibmiphp › webinar › Day 1.pdfK À À ] Á