IBM i Developers Share RPGLE Pattern to Automate User Access Provisioning

·1 views

A developer has published a production-tested RPGLE pattern on DEV Community that automates user access provisioning on IBM i without middleware or external servers. The system works by reading JSON request files dropped into an IFS inbox directory, which a scheduled RPGLE job periodically scans and processes using SQL and IBM's QSYS2 system views. Each request specifies a target user and a model user, and the program clones the model's profile and entitlements to the new account using a CL wrapper around the CPYUSRPRF command. The solution uses RPG's DATA-INTO opcode with a YAJL-based parser to deserialize JSON directly into data structures, eliminating manual token parsing. An audit trail is maintained by writing history records and emitting JSON audit events, addressing a common compliance gap in manual access provisioning workflows.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Why Python Raises UnboundLocalError and How to Fix It Correctly

Python's UnboundLocalError confuses developers because the variable in question visibly exists elsewhere in the code, yet the error still occurs. The root cause is that Python scans an entire function body before executing it, and any variable assigned anywhere inside the function is pre-marked as local throughout that function. This means a line like 'count += 1' causes Python to treat 'count' as a local variable, making the outer module-level 'count' inaccessible within that function. The cleanest fix is usually to pass the value as a parameter and return the updated result, avoiding shared mutable state altogether. When a function must modify a module-level variable, the 'global' keyword explicitly instructs Python to reference the outer scope instead of creating a local shadow.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

AWS Workshop Day 1: Hands-On Training Covers S3, CloudFront, and EC2 Basics

A two-day cloud workshop focused on AWS fundamentals kicked off with its first session covering core infrastructure concepts. Participants logged into the AWS Management Console and learned how AWS Regions and Availability Zones support global reliability and low latency. The session included practical exercises with Amazon S3, where attendees created storage buckets, uploaded files, and served content via pre-signed URLs and a CloudFront CDN distribution. Learners were also introduced to Amazon EC2, launching virtual instances, connecting via SSH, and deploying the Nginx web server. The session provided a foundational overview of cloud storage, content delivery, and compute services on AWS.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Gas Audit Flags $10–30M Annual Inefficiency in Bybit's Smart Contracts

A gas-optimization audit of Bybit's on-chain smart contracts, covering Ethereum Mainnet and L2 networks Optimism, Arbitrum, and zkSync, was completed on 16 September 2026. The audit, conducted by a senior DeFi security researcher, reviewed all contract components tied to Bybit's approximately $15.1 billion TVL. A total of 29 findings were identified across categories including unbounded loops, excessive storage operations, and inefficient calldata handling, with unbounded loops posing the highest risk of transaction failures. The protocol received a gas-risk score of 3 out of 10, indicating no critical security vulnerabilities but notable inefficiencies. Left unaddressed, these issues could result in an estimated $10–30 million in avoidable gas fees annually given current transaction volumes.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

SQL JOIN Types Explained: Inner, Left, Right, Full Outer, and Self Joins

A SQL JOIN combines rows from two or more tables based on a related column, eliminating the need to run separate queries and match results manually. An INNER JOIN returns only the rows where there is a matching value in both tables. A LEFT JOIN returns all rows from the left table along with matching rows from the right table, filling unmatched columns with null values. A FULL OUTER JOIN returns all rows from all involved tables, useful when a complete view of combined data is needed. A SELF JOIN allows a table to be joined with itself, useful for comparing rows within the same dataset.

0 comments Read more at DEV Community